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:
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.
On Jun 19, 2026, at 1:24 PM, 'Ray Bon' via CAS Community <cas-...@apereo.org> wrote: