I have worked with CAS 4.1 in the past and in that version, there was no way to extend the life of a TGT ticket without a user attempting to log into another CAS registered service prior to the expiration of the TGT. What this meant was that if a user used CAS to log into a registered service, and continued to be active in the local application longer than the TGT timeout, and then attempted to then log into a different registered service (application), they were prompted to log in to CAS again. In CAS 6.2+ is there a way to update the TGT to remain alive as long as the registered service application is being used (and local app session is valid)? I don't want to use the 'remember me' and allow a user to have a valid CAS TGT if they are not actively using one of the registered services, but if they are using a registered service I would like a way to ensure the TGT remains alive.
Thanks, Ed -- - 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/a3e31a8a-b911-4cb0-af37-f9660ec228e4n%40apereo.org.
