Service Registry
CAS allows you to declare services that may be used for CAS authentication. The service registry stores the services together with metadata and thus controls the behavior of the CAS.
There are various implementations that can be used for the service registry. We currently use the JSON Service Registry, in which the services are stored as JSON and are loaded into the memory at runtime.
A central storage location is defined for the registry, but this may differ depending on the Stage currently used.
If the CAS is in production mode, the services are loaded from the path /etc/cas/services/production. The services are created dynamically based on the actually installed Dogus.
For development mode, static services for the protocols CAS, OAUTH and OIDC are declared under the path /etc/cas/services/development, which apply generically for the respective protocols.
There is no differentiation between individual applications.
Services are usually created during the installation process of a dogu. If a dogu has a dependency on the CAS, the ExposedCommand service-account-create is called during the installation, which creates the service as a JSON configuration in the service registry.
Configuration templates are used for this, which are stored under the path /etc/cas/config/services. Depending on the input parameters and the type of protocol used, various Properties are filled,
which are then used by CAS internal templates.
These templates are referenced by their name and serve as a template for the CAS services generated in the memory. They can be found under /etc/cas/services/templates.
The final generated JSON files in the service registry always follow the naming convention <application>-<serviceID>.json.