Yes the config file is being written to /etc/cas1/config. What's interesting is that some of the other properties are being accepted and some are not. It looks like ones defined already in application.properties are not being overriden.
On Thursday, February 15, 2018 at 11:21:43 AM UTC-6, rbon wrote: > > Kevin, > > Is the config file being written to /etc/cas1/config? > Do you still have the same problem when using /etc/cas/config? > > Ray > > On Thu, 2018-02-15 at 07:05 -0800, Kevin Liu wrote: > > Hello, > > It is my understanding that cas.properties should override whatever > properties are in WEB-INF/classes application.properties. Is this correct? > > If so, I'm having trouble overriding > "cas.authn.accept.users=casuser::Mellon". With a blank value in > cas.properties and "cas.authn.accept.users=casuser::Mellon" in > application.properties, I'm still getting status authentication warning. > > It seems as if changing values in cas.properties don't have an effect, > only when I change the values in application.properties. > > The only thing I did differently is instead of pointing to > /etc/cas/config, I have it pointing to /etc/cas1/config (this is due to > allow multiple cas instances on the same box). Can I not do this? > > -- > Ray Bon > Programmer analyst > Development Services, University Systems > 2507218831 | CLE 019 | [email protected] <javascript:> > > -- - 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/3d309703-7523-4372-895c-99679147a4ad%40apereo.org.
