The CAS client currently doesn't support single sign out in a clustered environment. Its possible we may add one (we might need it at Rutgers) but if you can't wait for that (if it happens), we're accepting patches that add that feature :-)
Cheers, Scott On Tue, Jun 9, 2009 at 3:58 AM, Giorgio R. <[email protected]> wrote: > In my solution I have : > > 1) CAS server installed in one front-end Apache + Tomcat. > 2) three single sign on clients applications installed in > two front-end Apache and four tomcat in a balancing > configuration round robin (sticky session). > > All work fine but when CAS server send a logout request to one of > these 3 apps i get often an exception because CAS server doesn't know > wich tomcat contact. > How can i solve ? > thanks at all > Giorgio > > > -- > 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-dev > -- 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-dev
