Hi, This is a known issue from RC1 : https://issues.jasig.org/browse/CAS-1326. Please upgrade to RC2-SNAPSHOT. RC2 is coming very soon... Best regards, Jérôme
2013/10/22 tgjorgoski <[email protected]> > Hi, > > We are having trouble implementing the single sign out using the CAS > 4.0.0-RC1. > The client library is spring-security-cas 3.1.4 > > The single-sign-on works great - for example after logging through > foo-service web-page we can visit bar-service web-page without logging > again, and also proxy tickets work great, so after logging-in, foo-service > can call bar-service using proxy tickets. > > However, after doing any of this, and then visiting the cas/logout page, > CAS gives a message that it was successfully logged-out, but as far as I > can tell no callbacks to the services that were used happen. So, after > visiting cas/logout page, you can still visit foo-service and it shows you > as logged in. > > I've put breakpoints within the SingleSingoutFilter within the > foo-service, and it doesn't even get started in the case when visiting > cas/logout page, so it seems there is no callback at all to the > foo-service. > Also, I put a breakpoint at > org.jasig.cas.logout.LogoutManagerImpl.performLogout within CAS, and that > method is not executed at all. > > Any idea what could be wrong? > -- > 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
