1) Cas management uses configuration only partly, someparts are taken from I dont know where ... cas.server.name: https://sso-fe1.arendus.kit cas.server.prefix: https://sso-fe1.arendus.kit cas.host.name=https://sso-fe1.arendus.kit cas.mgmt.adminRoles=ROLE_ADMIN cas.mgmt.userPropertiesFile=file:/opt/tomcat/CAS/user.properties cas.mgmt.serverName=https://sso-fe1.arendus.kit
Results in: https://sso-fe1.arendus.kit/login?service=http%3A%2F%2Fsso-be1.arendus.kit%3A8081%2Fcas-management%2Fmanage.html 8081 can only become from Tomcat server.xml, the same with host name. Serious issue enforcing of deploying management app in different VM. 2) cas.serviceRegistry.jpa.ddlAuto=update Every single time app. server is restarted, configuration is reloaded from static list and not UPDATE'd but again INSERTed to database. 3) https://apereo.github.io/cas/5.1.x/installation/Configuring-Custom-Authentication.html This does not work at all. Only way was to overwrite your original source files -got solved my need for custom authentication (which 99.9% of time is the need for users) . Credential is hardcode mapped somewhere to UsernamePasswordCredential. This section should be really documented much more with working examples. -- You received this message because you are subscribed to the Google Groups "CAS Developer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-dev/.
