In our meeting yesterday I just found out that we're moving Single Signout to post CAS 3.0. It will remain in the sandbox but it will not be part of the official distribution (I'm hoping i can push it out quickly after if possible.)
In our meeting yesterday I just found out that we're moving Single Signout to post CAS 3.0. It will remain in the sandbox but it will not be part of the official distribution (I'm hoping i can push it out quickly after if possible.)
any updates on Single Sign Out?![]()
Go to the CAS site
http://www.ja-sig.org/products/cas/
and search for "signout"
Thank you very much Luke.
Here's an interesting post I found by following your lead:
VT CAS Server Software Architecture
Cheers!
By following the CCCI recommendations, I was able to implement a very effective signoff from our 2.X CAS implementation. The key feature I had to add was a new ACEGI filter that verified the user was still enabled b4 proceeding with the rest of the ACEGI chain. The CCCI recommendation suggested detecting a "-" infront of the service ticket to signal the app to disable the user.
So, when an app logs out, CAS sends a logout command to all logged in apps and they mark that user as disabled. When the user comes back, the login enabled filter detects they are disabled and invalidates the session.
I can provide more details if needed but it works great for us.
Sleep is for the weak