hello! So i'm coming off a successful deployment of 6.1 of cas and cas-management, and trying similar deployment practices with the 6.5 branches. I've run into some things I wanted to mention to see if i'm just doing it wrong.
I can't leave well enough alone and like to have the cas.properties, and management.properties files in custom locations, along with services, and users.json, etc. I've had great success with using the SPRING_APPLICATION_JSON environment variable to define cas.standalone.configurationDirectory, which tells cas and cas-management where to look for certain config files. CAS 6.5.5 is working beautifully with this, but CAS-Management 6.5.5 is choking. Despite the catalina.out log stating that both cas and cas-management have found the cas.properties and management.properties files, cas-management appears to not read the contents. Settings like the JSON service Registry folder location will not take if I just define them in the management.properties file. CAS picks up on the location defined in its cas.properties file, but not CAS-Management. I have just had luck defining it's location in the SPRING_APPLICATION_JSON environment variable using the same property as is written in the management.properties file. That got that part working, but then cas-management started to say it was looking in /etc/cas for things again, and failing. Anyone have any similar experiences? thanks! -- - 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/b5365450-8e06-4c75-ab88-e08cbcf66c23n%40apereo.org.
