The services registry of CAS is empty and has no service definitions. Applications that wish to authenticate with CAS must explicitly be defined in the services registry.
Jérémie,
Provided you have not configured persistent service storage with jpa, ldap, etc…. you can find an example service definition file
At this location <cas-overlay-directory> target/war/work/org.apereo.cas/cas-server-webapp-tomcat/WEB-INF/classes/services/HTTPSandIMAPS-10000001.json
For example,
{
"@class" : "org.apereo.cas.services.RegexRegisteredService",
"serviceId" : "^(https|http)://cas-server.some.edu/cas-management.*",
"name" : "CAS Services",
"id" : 10000004,
"description" : "This service definition authorizes the cas services management application.",
"evaluationOrder" : 10000
}
I’ve made sweeping assumptions here, but hopefully this will give you enough to get going.
https://apereo.github.io/cas/5.1.x/installation/JSON-Service-Management.html
Good luck!
Erik Mallory
Server Analyst
Wichita State University
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/e4d827cc-34b3-403e-a9e2-4bfddb3be5e6%40apereo.org.