Hi all, I'm wondering if any thought has been given to implement a mechanism for clustered CAS client servers to each receive logout requests from the CAS server?
We have 2 web servers independent of each other behind an f5 load balancer. We're not session sharing, and don't want to store the CAS sessions in a backend database (single point of failure). Presently the CAS logout request is sent and gets routed to either web server. If the user happened to have their session on the other server, they won't be logged out. The ideal solution: 1) domain.edu/app1** has been configured to send logout requests to server1.domain.edu** and server2.domain.edu** 2) User logs into domain.edu/app1 3) User logs out 4) Logout request is sent to server1.domain.edu and server2.domain.edu I am aware of the ability to store sessions in a database, but this creates a single point of failure. Thanks, Matt -- 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
