There are two frontend-related flows, one for cenTaur and one for censhare Server with censhare WP. Which flow is used, depends on the browser application that a user accesses: cenario for cenTaur and censhare WP for censhare Server with censhare WP.
Flow for censhare Server with censhare WP
censhare WP sends URL-based requests to the Cloud Gateway. The Cloud Gateway determines how to handle the request:
- If a user is not yet authenticated, the user is redirected to the Authentication microservice which uses Keycloak. Keycloak can maintain the accounts by itself or connect to an external LDAP provider.
- Requests for the web frontend files are routed to the Static Resource Server (SRS). The SRS hosts several webpack bundles that contain all static files for the web frontend. These bundles are sent to the web browser.
- Data requests are routed to the censhare Server. The censhare Server offers endpoints for REST, websocket and file upload.
Flow for cenTaur
cenario sends URL-based requests to the Cloud Gateway. The Cloud Gateway determines how to handle the request:
- If a user is not yet authenticated, the user is redirected to the Authentication microservice which uses Keycloak. Keycloak can maintain the accounts by itself or connect to an external LDAP provider.
- Requests for the web frontend files are routed to the censhare Platform microservice. censhare Platform hosts several webpack bundles that contain all static files for the web frontend. These bundles are sent to the web browser.
- Data requests are routed to the GraphQL Gateway. Data requests are defined using GraphQL. GraphQL is a query language to define APIs. For the processing of data requests, see Data Handling.