Hello Ray, I have thought about the user implications and it's not currently a large concern because I'm looking at this more from a security point of view.
My CAS sessions are longer than that of the services, but I want an expired user to be stopped from accessing all services as soon as possible. Once I'm able to establish that part of the functionality then I can tweak the user experience, if needed. For the time being I'm okay with the user being forced out and receiving a message that indicates their expiry, if/when they try to log in again. What I need to know is whether it's actually possible to insert logic into CAS that will: 1. Monitor my user table and identify expired users from the user expiry column. 2. Expire their TGT. 3. Initiate SLO to log them out of registered services. Thanks! -- - 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/897a1a81-fe6e-4500-9a0a-788510acee2e%40apereo.org.
