Zum Hauptinhalt springen

Kundenportal Hosting Guide

🤖 Generated with Claude Code

✅ Reviewed by Moritz Haslhofer

Co-Authored-By: Claude (noreply@anthropic.com)

External documentation for Makler IT / Security teams.

1. Overview​

The Kundenportal is a multi-tenant web application (SPA) that enables Endkunden to access their Polizzen, documents, and submit Schadenmeldungen.

Architecture Summary:

  • SPA Frontend: Hosted on Together-Cloud (*.myversum.at)
  • EndcustomerApi: Runs on customer infrastructure (inside CCAOnline)
  • Customer Data: Remains on customer infrastructure (Blue zone)

See architecture diagram: hosting-network-flow.svg

Why This Architecture?​

GoalImplementation
Data ProtectionCustomer data never leaves your infrastructure. Together-Cloud only hosts the SPA shell and static assets.
No Customer DeploymentTogether manages SPA updates centrally. No frontend deployment required on customer side.
Version CompatibilitySPA version auto-selected based on your CCAOnline version. No coordinated upgrades needed.
Simple Firewall RulesTwo static IPs to whitelist for Together services (see Section 3.2).

2. Infrastructure Requirements (MUST)​

No additional servers are required — the Kundenportal uses the existing CCAOnline infrastructure. That infrastructure MUST provide:

  • CCAOnline: a current version with Kundenportal support enabled
  • Database: the existing CCA database, exposing the ecav2 schema views
  • NotificationApi: reachability of the Together-Cloud NotificationApi, which delivers MFA codes and activation emails

For CCAOnline server requirements, refer to the CCAOnline documentation.

3. Network Configuration​

3.1 Outbound Firewall Rules (MUST)​

CCAOnline MUST have outbound HTTPS (443) access to the following Together-Cloud endpoints:

DestinationPurpose
*.api.cca.onlineManagement API
*.cca.onlineMFA email delivery
*.servicebytogether.atIdentity Server
*.myversum.atPortal hostnames

3.2 Inbound Requirements (MUST — CCAOnline Routes)​

The following CCAOnline routes MUST be reachable from the internet, over HTTPS only:

PathCalled ByPurpose
/healthTogether-Cloud, EndkundeCCAOnline health + version (SPA version selection)
/endcustomer/*EndkundeEndcustomerApi - Auth, Account, API endpoints
/api/*Together-PlattformIntegration callbacks (e.g., /api/togetherSign/callback)

Together Service IPs​

ServiceSource IPEndpoints
Together-Cloud (Management Server)40.91.210.71/health
Together-Plattform193.80.22.145/api/*

These IPs MUST be whitelisted for server-to-server communication. Endkunde requests originate from the public internet.

Important: The /health endpoint MUST return details.applicationVersion. Together-Cloud uses this to determine which SPA version to serve.

For detailed API documentation, see SwaggerHub EndCustomerApi.

Note: The SPA may call routes with double slashes (e.g., //endcustomer/token). Your reverse proxy MUST handle these correctly.

3.3 DNS Configuration​

Custom Domain Setup:

To use a custom domain (e.g., portal.makler.at), a CNAME record MUST be configured, pointing to the Together-Cloud hosting:

portal.makler.at  CNAME  <provided-by-together>.myversum.at

Contact TOGETHER support for the specific CNAME target.

4. SSL/TLS Certificates​

SSL/TLS certificates for *.myversum.at are managed by Together-Cloud. No customer action required.

For custom domains, certificate provisioning is handled automatically via Together-Cloud after DNS configuration is complete.

5. Security & Data Classification​

5.1 Data Flow​

Endkunde Browser
│
├─── SPA assets ───> Together-Cloud (Yellow zone: public data only)
│
└─── API requests ──> CCAOnline (Blue zone: protected customer data)

5.2 Data Residency​

ZoneDataLocation
Yellow (Together-Cloud)SPA code, static assets, portal configWest Europe (EU)
Blue (Customer)Polizzen, documents, Endkunden dataCustomer CCAOnline server

Together-Cloud infrastructure is hosted in West Europe (EU) for GDPR compliance.

Protected customer data never leaves customer infrastructure. The SPA retrieves data via authenticated API calls to CCAOnline.

5.3 Security Measures​

Together-Cloud is protected by:

  • Application Gateway WAF v2 - Web Application Firewall
  • Microsoft Defender for Cloud - Security monitoring

5.4 Authentication Flow​

  1. Endkunde navigates to portal URL
  2. SPA loads from Together-Cloud
  3. SPA redirects to CCAOnline for authentication (MFA)
  4. CCAOnline issues Bearer token
  5. SPA uses token to access EndcustomerApi

5.5 Customer Infrastructure Security​

Planned: Customer infrastructure security requirements documentation.

6. Integration Points​

EndpointLocationPurpose
https://{portal}.myversum.atTogether-CloudPortal frontend (SPA)
https://kundenportal-mgmnt.api.cca.onlineTogether-CloudManagement API
https://notification-api.cca.onlineTogether-CloudMFA email delivery
{ccaonline}/endcustomer/tokenCustomerOAuth token endpoint
{ccaonline}/endcustomer/authorizeCustomerOAuth authorization
{ccaonline}/endcustomer/api/*CustomerEndcustomerApi (data)

7. Health Check Verification (MUST)​

The following MUST be verified before go-live:

  1. Outbound connectivity: CCAOnline can reach Together-Cloud endpoints (Section 3.1)
  2. DNS resolution: Custom domain resolves correctly (if applicable)
  3. CCAOnline health: {ccaonline}/health returns:
    • "status": "UP"
    • "details": { "applicationVersion": "x.x.x" }
  4. EndcustomerApi health: {ccaonline}/endcustomer/health returns healthy
  5. Portal load: Navigate to portal URL, verify SPA loads
  6. Authentication: Complete login flow with test Endkunde

Note: Together-Cloud (40.91.210.71) periodically checks /health to verify availability and determine SPA version compatibility.

8. Support​

For questions or support, contact TOGETHER: