Akash,
The TGT is the server side session identifier; the SSO session. 4m is short. Given that the service ticket life is longer, it is possible that a service will try to validate it [and fail] after 4m; requiring the user to re-authenticate.
It is possible that the minimum TGT lifetime has changed. I use 2m on my local to make testing easier.
It is also possible that the ticket store has limits (we use hazelcast).
If you are planning to use single logout, the TGT may be purged prior to your services sending a logout request; thus preventing SLO.
Is this for testing or production?
What are you trying to achieve with a short SSO session length (there may be an alternative method)?
What is the minimum time that is stored?
Ray
From: 'Akash Mohapatra' via CAS Community <cas-...@apereo.org>
Sent: November 24, 2025 07:51
To: CAS Community <cas-...@apereo.org>
Subject: [cas-user] How to set ttl for ticket created in DynamoDB