> However in my case application is having multiple WAR(s) in each tomcat, > the user is exposed only one URL and each WAR is having its own context.
Not sure I follow "exposed only one URL" part of that scenario. > Each WAR authenticates against CAS. If each WAR is having its own context > then CAS will post logout request to each individual WAR. Let's get away from deployment-related matters like how you deploy WAR files. CAS will attempt send a SAML LogoutRequest to every application that requested a service ticket. The LogoutRequest will be posted to the URL that was originally presented to CAS in the service parameter of the querystring, e.g. https://cas.example.com/login?service=https://service.example.com. If the logout POST URL happens to be for a clustered service, the service must be responsible for handling the message posted to any member of the cluster. > With clustering the HttpSession clearing from the other tomcat will be taken > care of Clustering will cause all replicated session state, including session invalidation, to be propagated among all nodes in the cluster. 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
