> Both the tomcat applications is the same, so when the CAS callback for > clearing the HttpSession occurs only one of the HttpsSession will be cleared?
Yes, in your clustering configuration. Additionally, the node that handles the CAS LogoutRequest message may not be the one holding the session. (The LogoutRequest is sourced from CAS, not the client, so sticky sessions won't help.) The most straightforward solution to this limitation is to enable Tomcat session clustering. 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
