If you have more than one cas server (and consequently, more than one hazelcast server), the tickets are shared and maintained by the hazelcast cluster. As long as at least one cas server is running, the cas sessions will be preserved. You may have to upgrade to get that capability. If you want to use an external hazelcast, the one started by cas would not be used. This may required appropriate config in the external instance.
Ray On Tue, 2025-02-25 at 22:26 -0800, 1000milesdrunk wrote: You don't often get email from specsudhar...@gmail.com. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi, I have a doubt where i want to separate hazelcast from cas so that whenever I restart cas the logged in users dont get logged out since cas is restarting hazelcast ,so I want to seperate cas and hazelcast so that the restart does not affect the logged in users I am currently having CAS 5.3 What property to add for that or what to remove currently using cas.ticket.registry.hazelcast.cluster.members=hazelcast1.enhancesys.com:5701 cas.ticket.registry.hazelcast.cluster.instanceName=sessionConfig cas.ticket.registry.hazelcast.cluster.port=5701 tried cas.ticket.registry.hazelcast.cluster.enabled=false which does not start the cas itself,what to do -- - Website: https://apereo.github.io/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 cas-user+unsubscr...@apereo.org. To view this discussion visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/760e79e25540d480434f9613af31c4530b2c92d6.camel%40uvic.ca.
