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
Ria,
The simple answer would be to upgrade.
Do you have documentation for Cas 5?
Perhaps I misunderstood the session issues. It could be that cas 5 does
not have the feature to cluster delegated saml auth. It may be that you
have a missing encryption key for saml storage (so cas will generate
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
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
