Hi, When you call the CAS logout, the CAS server destroys your SSO session (CASTGC cookie) and call all the services you have browsed to tell them to end the application sessions. So, even if you have set a very long duration for your CAS session, it will be expired. The only caveat with the default CAS logout is when you have clustered applications with front session affinity. In that case, you need to share your application session accross all nodes of your cluster or use some custom front logout mechanism. An experimental feature is available in CAS 4.0, even if CAS clients are not ready yet to support it (hope we can do that pretty soon). Best regards, Jérôme
2013/9/17 Stefan Holodnick <[email protected]> > Currently, we've had some issues with our being signed out of their > courses in the Canvas LMS while taking a test. We think it might have > something to do with the tickets expiring. The time that we have them set > to expire is fairly long. Another thought was that maybe it has to do with > single sign-out. Maybe they are logging out of another SSO application > while they are still in CAS? > > Has anyone has these problems with their LMS or other applications? What > have you done with ticket expiration to manage this? How do you handle > single sign-out? I'm curious as to how you tackled this problem. Any help > is appreciated. > > Stefan Holodnick > Online Services Developer > Kirtland Community College > > -- > You are currently subscribed to [email protected] as: [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
