Thank you for your answer. Is this the only way to succeed this in cas version 5.2.9?
I see, probably in a greater version of cas, some other options that I am not sure however if exist in this version of cas. e.g set the config cas.authn.saml-idp.core.session-storage-type=TICKET_REGISTRY . Is something similar possible in the cas version I am using? Thanks Ria On Monday, September 26, 2022 at 6:36:07 PM UTC+3 Ray Bon wrote: > Ria, > > The session is managed by the application container; tomcat, jetty, etc. > Look into clustering the container. > > Ray > > On Mon, 2022-09-26 at 07:00 -0700, Freedom K wrote: > > Notice: This message was sent from outside the University of Victoria > email system. Please be cautious with links and sensitive information. > > > Hi everyone, > > I am using CAS vesrion 5.2.9 with saml okta as authenticator and I am > searching for a way to share the sessions between two cas servers. > This is because the service is stored in the session and if the login > requests starts in cas 1 but after the okta authentication is redirected to > cas 2 the service /session is not recognized by cas 2. > Up to now I am using ehcache to replicate the tgt and st , but for the > sessions I have not found a way yet. > > Thank you, > Ria > > -- - 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/58fca83f-f18b-48ed-9917-8ff9393bf297n%40apereo.org.
