> It seems like the answer to your Single Sign Out issue in a load balanced > environment is fairly simple. Use a shared session mechanism instead of using > sticky sessions for your load balanced servers.
This is incorrect. Since the request is sourced differently from the CAS server, it naturally does not contain the session identifier needed to load the session from _any_ store, shared or otherwise. Please review the patch I referenced; it's one potential solution that has been thoroughly tested. While shared storage is part of the solution, it's not session storage alone that needs to be shared. 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
