Hello,
I have a question regarding session timeout behavior after migrating from CAS 6.6.15 to CAS 7.3.5. In our CAS server, we have the following ticket configuration: *cas.ticket.tgt.hard-timeout.time-to-kill-in-seconds=7140cas.ticket.st.time-to-kill-in-seconds=120* The TGT timeout is configured to be almost *2 hours*, and this configuration was already working before the migration. However, we have an external application integrated with our CAS SSO server using CAS authentication. This application logs users out every *1 hour*, even though the CAS TGT is still supposed to be valid for nearly *2 hours*. Because of this behavior, I suspect the application is not taking the CAS session lifetime into account and may be managing its own session timeout. Has anyone encountered a similar situation? Do you have any recommendations on how to investigate whether the timeout is coming from CAS or from the client application itself? Thank you for your help. -- - 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 [email protected]. To view this discussion visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/52c0249e-443f-47da-8534-25d0dd8b61bbn%40apereo.org.
