Baron, We use tomcat/bin/setenv.sh. Command line parameters go there:
# CAS Config direct file access CATALINA_OPTS="$CATALINA_OPTS -Dcas.standalone.configurationDirectory=/home/uvtomcat/config" CATALINA_OPTS="$CATALINA_OPTS -Dspring.config.additional-location=/home/uvtomcat/config/bootstrap.yml" export CATALINA_OPTS Ray On Wed, 2021-04-07 at 06:57 -1000, Baron Fujimoto wrote: Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information. Just bumping this again to see if anyone has any guidance or pointers to clarifying documentation. On Thu, Apr 1, 2021 at 11:08 AM Baron Fujimoto <[email protected]<mailto:[email protected]>> wrote: 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 <[email protected]<mailto:[email protected]>> :: UH Information Technology Services minutas cantorum, minutas balorum, minutas carboratum desendus pantorum -- Baron Fujimoto <[email protected]<mailto:[email protected]>> :: UH Information Technology Services minutas cantorum, minutas balorum, minutas carboratum desendus pantorum -- Ray Bon Programmer Analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected]<mailto:[email protected]> I respectfully acknowledge that my place of work is located within the ancestral, traditional and unceded territory of the Songhees, Esquimalt and WSÁNEĆ Nations. -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/768ae95814d01ee03d4e508cb91cd6c2a25be628.camel%40uvic.ca.
