The path of a request, end to end
Flows walked through across all parties: from login to the row in the database, the path of the token, the tenant check in both operating modes, and what happens when something fails.
Topics in this subject area
- 1.From login to the data
A person logs in and opens a list. Every step through browser, BFF, Keycloak, CIAS and CDMS to the database and back, in both operating modes.
- 2.The path of the token
Where the token is created, where it is stored, who exchanges it and who reads it, until it arrives at CDMS as a RequestContext.
- 3.The tenant check in both operating modes
How the tenant gate asks: embedded through a method call, standalone through HTTP, with cache, timeout and error handling.
- 4.When CIAS is not reachable
What CDMS does in standalone mode when CIAS goes down: keep serving known tenants, reject unknown ones, tenant-bound attributes cannot be read.
- 5.A write across all layers
A form is saved: from the click through BFF, token check, permissions, validation, hooks, saving, audit and commit to the response.