Trenton, You are correct. If you are using an in memory ticket store, they would be lost anyway. It is not too difficult to add them to the config (copy paste) and it removes the nag ;)
Ray On Mon, 2019-02-11 at 10:51 -0700, Trenton D. Adams wrote: Good day folks, I just wanted to confirm. We're starting out with a single instance of the newer cas. CAS is generating new encryption/signing keys on each start. I think that's totally fine for single instance, and I don't actually have to store those in the configs, correct? It just implies that a restart will create new keys, resulting in the invalidation of existing tickets. Thanks. -- Trenton D. Adams Senior Systems Analyst/Web Software Developer Applications Unit - ITS Athabasca University (780) 675-6195 It is only when you are surrounded by a supportive team, that you can achieve your best. Instead of tearing people down, try building them up! -- This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- -- Ray Bon Programmer analyst Development Services, University Systems 2507218831 | CLE 019 | [email protected] -- - 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/1549907876.3634.2.camel%40uvic.ca.
