Hi, I assume you talk about CAS 3.5.2. The logout : https://github.com/Jasig/cas/blob/3.5.x/cas-server-core/src/main/java/org/jasig/cas/web/LogoutController.java#L82 will call https://github.com/Jasig/cas/blob/3.5.x/cas-server-core/src/main/java/org/jasig/cas/CentralAuthenticationServiceImpl.java#L152 to destroy the TGT. In this method, the TGT is retrieved from the ticket registry : in case of an expired ticket, you will get null and no logout will be performed for it. Best regards, Jérôme
2013/8/9 Tom Freestone <[email protected]> > We are using a ehcache backed ticket registry. We have implemented > single-sign-out on our cas server. I was curious how the single-signout is > tracked in the ticket registry? > > If you configure ehcache for 100,000 TGT's and only 60,000 are active > (e.g. not evicted from ehcache), you will see the other 40,000 objects (in > a heap dump) with old TGT's. Will the remain 40,000 "inactive" still have > their single-signout data associated with them? > > I looked around the docs but there was only configuration information. > Where can I look for implementation details. Thanks! > > tom > > -- > > ***************************** > Tom Freestone > ([email protected]) > ***************************** > > -- > 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
