On Fri, Jan 25, 2013 at 8:27 AM, Richard Frazer <[email protected]> wrote: > I am using CAS Server 3.4.11 and am attempting to get single sign out to > work. It all works fine for applications that are using service tickets, > however, applications for which I am using proxy tickets aren’t getting the > single sign out request. I stepped through the server code, and it appears > that the initial TGT gets the expire() call, which calls all the service > ticket services. However, the expire method for child PGTs isn’t being > called. The PGT is getting removed from the db via the > JpaTicketRegistry.deleteTicketAndChildren() call. > > Is this by design or should proxied services be getting single sign out > calls as well?
Looks like an oversight. Feel free to open a JIRA. Best, Bill > > Thanks, > Richard Frazer > > > -- > 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
