3rd day in a row trying to tackle my logout issue. I've further delved into what actually arrives at my client app and figured that the logout-request from CAS arrives as a GET request and doesn't contain the parameters the Logout-Filter requires (judging from the client's source). I have also upgraded to the latest version of the Java client (3.1.5) which didn't make difference though (besides some nasty warn-exceptions on startup).
Is there really nobody out there having a slight idea what the problem could be? Any help would really be appreciated! Regards, Martin Am 11.05.2009 um 23:01 schrieb Martin Simons: > Another bit of information: On the CAS server side I see log-entries > when logging in, but there is no activity in the log whatsoever when > logging out? This is really confusing. Any ideas? > > > Am 11.05.2009 um 21:35 schrieb Martin Simons: > >> M, >> >> the logout-problem is still riddling me. I've followed your advice >> and tried to set up all filters with the same scope. Didn't work >> either though, just leading to an infinite redirect loop. Maybe I >> should post my general application setup after I provided you with >> my filter mappings already: >> >> The app is a wicket app mounted under "/app". There are freely >> accessible pages and restricted pages, the latter mapped to /app/ >> account/* and /app/credits/* according to the mappings. >> >> If accessing the application via the root (meaning /, not /app), a >> JSP redirects to the app-folder which again will let Wicket >> redirect to the configured main page (namely /app/account/index). >> >> If firing a logout within CAS, I get the following log-entry: >> >> 2009-05-11 21:33:52,587 DEBUG >> [org.jasig.cas.client.authentication.AuthenticationFilter] - <no >> ticket and no assertion found> >> 2009-05-11 21:33:52,587 DEBUG >> [org.jasig.cas.client.authentication.AuthenticationFilter] - >> <redirecting to >> "https://auriga:8443/cas/login?service=http%3A%2F%2Fauriga%3A8080%2Faquila%3Bjsessionid%3D37D52120FCD6D42934A5620BBCF76CB3 >> >> "> >> >> That's all. No log-entry tells me anything about the logout itself, >> just about some request coming in that obviously isn't handled the >> way it should be. >> >> Any idea anybody? >> >> Regards, >> Martin >> >> >> Am 08.05.2009 um 14:14 schrieb Marvin Addison: >> >>> You have the SSOutFilter listed first, which is correct. The only >>> other thing I would note is that the scope of your CAS filters is >>> not >>> consistent. Typically all CAS filters have the same scope, e.g. >>> url-pattern is same across all since the CAS filters work together >>> to >>> support the CAS protocol. You might try setting them up with the >>> same >>> scope and see whether that helps. >>> >>> M >>> >>> -- >>> 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 > > > -- > 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
