WORKERS AHEAD!
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.
InMemory Service Registry
This is an in-memory services management tool seeded from registration beans wired via Spring beans.
1
2
3
4
5
6
7
8
9
10
11
12
@Configuration("myConfiguration")
public class MyConfiguration {
@Bean
public List inMemoryRegisteredServices() {
final List services = new ArrayList<>();
final RegexRegisteredService service = new RegexRegisteredService();
...
services.add(service);
return services;
}
}
See this guide to learn more about how to register configurations into the CAS runtime.
Given registered services are injected into the context as Spring bean definitions, you will need to consult the project’s javadocs to learn more about the CAS service API, and how to inject various other components into the service definition.
This component is NOT suitable for use with the service management webapp since it does not persist data. On the other hand, it is perfectly acceptable for deployments where the hard-coded configuration is authoritative and good-enough for service registry data and the UI will not be used where there only exist a handful of applications integrated with CAS.
Auto Initialization
Upon startup and configuration permitting, the registry is able to auto initialize itself from default JSON service definitions available to CAS. See this guide for more info.