In our CAS 5 deployment, I had changed the CAS config directory with an overlay for the file
/webapp/cas-server-webapp-resources/src/main/resources/bootstrap.properties
that set it to a cas role account user, like so
spring.cloud.config.server.native.searchLocations=file:///home/cas/cas/config
I'm working on upgrading to 6.3 now, and would like to do something equivalent rather than using the default /etc/cas/config
The CAS docs at <
https://apereo.github.io/cas/6.3.x/configuration/Configuration-Server-Management.html#property-overrides> seem to suggest that the file src/main/resources/bootstrap.properties is still relevant, and provides the default(?) example:
spring.cloud.config.server.native.searchLocations=file:///etc/cas/config
However, when I look at webapp/cas-server-webapp-resources/src/main/resources/bootstrap.properties from the repo, I see:
# Do NOT modify this line below.
# If you wish to change the configuration directory, it's best to not
# overlay this file, but specify the directory location via command-line
# parameters or system properties via -D.
# cas.standalone.configuration-directory=/etc/cas/config
I *think* we want to use the default standalone profile to be compatible with our current CAS 5 deployments? But if so, I'm not sure what the recommended best practice is to achieve this given what I've seen. Do we set searchLocation in a bootstrap.properties overlay, or do we heed the advice to not mess with that there? Or am I misunderstanding the relationship between spring.cloud.config.server.native.searchLocations and cas.standalone.configuration-directory for what we're trying to achieve? The comments suggest that we "specify the directory location via command-line parameters or system properties via -D". Are there explicit examples of how we would do this?
--
Baron Fujimoto <
ba...@hawaii.edu> :: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum desendus pantorum