You are viewing the development documentation for the Apereo CAS server. The functionality presented here is not officially released yet. This is a work in progress and will be continually updated as development moves forward. To view the documentation for a specific Apereo CAS server release, please choose an appropriate version. The release schedule is also available here.
The CAS spring cloud configuration server is able to consume properties and settings via the profiles outlined here. The server is constantly monitoring changes to the underlying property sources automatically, but has no way to broadcast those changes to its own clients, such as the CAS server itself, which would act as a client of the configuration server expecting change notifications to quietly reload its configuration.
Therefor, in order to broadcast such
change events CAS
presents various endpoints that allow the adopter
to refresh the configuration as needed. This means that an adopter would simply
change a required CAS settings and then would submit
a request to CAS to refresh its current state. All CAS internal components that are affected
by the external change are quietly reloaded
and the setting takes immediate effect, completely removing the need for container restarts or CAS re-deployments.
Most if not all CAS settings are eligible candidates for reloads. CAS should be smart enough to reload the appropriate configuration, regardless of setting/module that ends up using that setting. All is fair game, as the entire CAS web application inclusive of all modules and all relevant settings may be completely and utterly reloadable. If you find an instance where this statement does not hold, please speak up.
To see the relevant list of CAS properties, please review this guide.
CAS uses Spring Cloud to manage the internal state of the configuration. The configuration server that is provided by Spring Cloud embedded in CAS is constantly monitoring sources that house CAS settings and upon changes will auto-refresh itself.
In the event that the standalone configuration profile is used to control and direct settings and Spring Cloud configuration server is disabled, CAS will begin to automatically watch and monitor the configuration files indicated by the profile and will auto-reload the state of the runtime application context automatically. You may also attempt to refresh settings manually via the CAS admin screens.
Clients of the configuration server (i.e. CAS server web application) do also expose a
that allow one to refresh the configuration based on the current state of the configuration server and reconfigure
the application runtime without the need to restart the JVM.
1 curl -X POST https://cas.server.url/cas/actuator/refresh
See this guide to learn more about various monitoring endpoints, etc.