Hello! As I understand, by default CAS stores created tickets in memory. This leads to a problem: when we remove or add a node - other nodes cannot recognize its tickets, so authentication fails with "Ticket not recognized" exception.
We understood that just running multiple nodes of CAS is not an option. So, here is the question: is it a good idea to use some centralized storage for tickets, and connect multiple instances of CAS to it like on the attached diagram? Will it support dynamically adding and removing CAS servers? What will happen when one gets a ticket from an instance, and then validates it on any other instance? [image: Untitled Diagram.jpg] Thank you! -- - 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/1a726313-29d1-4164-a372-031a552bd404%40apereo.org.
