A single unit or separate services
The two topologies of CIAS next to CDMS: embedded in one process or as a separate service. What runs in each, who calls whom, why both must behave the same in the subject area — and how that relates to the operating mode of the data storage, SINGLE or MULTI.
CIAS embedded (a single unit)CIAS as a separate serviceEmbedded and standalone comparedConfiguration decides what runsSINGLE and MULTI across both modulesWhy both modes must behave the same in the subject area
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.
From login to the dataThe path of the tokenThe tenant check in both operating modesWhen CIAS is not reachableA write across all layers
Startup, provisioning, reconciliation
What happens before the first request arrives: cold start, registering the modules' roles and attributes with CIAS, a new tenant from start to finish, and the database schemas.
Cold start of an installationModules register roles and attributesA new tenant, end to endDatabases and schemas