There's a bug in CAS 3.2 (a missing "!") that reverses the logic to disable/enable Single Sign Out. My guess is you're running into that. I'm working on an RC1 of CAS 3.2.1 that should fix that.
-Scott On Tue, Mar 25, 2008 at 11:50 AM, Brian Dunbar <[EMAIL PROTECTED]> wrote: > I am having trouble getting the single sign out capability to work. I > have CAS and single sign on working nicely. I am using: > cas-server-3.2 > cas-client-3.1.1 > > I have configured my web.xml in my client application to use the > SingleSignOutFilter and session listener as described on the Wiki page: > > http://www.ja-sig.org/wiki/display/CASC/Configuring+Single+Sign+Out > > I have a link to /cas/logout on my application page. It shows me > successfully logged out on the page, but the application is still > logged in. It does not appear to ever get the callback for the logout. > > I have seen references to registering for SingleSignOut when the > application first authenticates but I have not been able to find > anything to configure to do this. Did I miss something there? > > I saw one post referencing SSL. I am not using SSL for my demo. Is > that an absolute requirement for SingleSignOut to work. > > Any ideas on where to look? > > Thank you, > > Brian > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > -- -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
