I should preface this with the fact that I don't really like what we are doing, but I liked it better than complicating our web server structure with a database. I think the "common data store"/"no data store" argument is core to my request, and I can explain my reasoning more if anyone is interested.
Our LoadBalancer catches logout requests that come from the CAS server and that are going to specific locations. It modifies that request and sends it with the original request as a parameter to a script that we wrote on the web server. The web server then processes the request and replicates it out to each web server. Each web server receives the logout, and for the server the user was on, they are logged out, for the other servers, then we just wasted some CPU cycles. The CAS client itself invalidates the user's session. Our script sits between the client and the server to replicate the logout command. Cheers Dave Wolowicz Manager of Web Services University of Victoria Systems [email protected] | (250) 721-6117 Call me toll-free over the internet: UVic-6117 -----Original Message----- From: Laura Griffel [mailto:[email protected]] Sent: February-24-11 7:03 AM To: [email protected] Subject: RE: [cas-user] Clustered CAS client logout request > If the CAS server does not do it, you need to catch the event, then replicate it to the other servers. To do > that you need to setup something to do the capture, and then something to do the mapping and replication. If > it was all in CAS it would be significantly simpler. Hi David, I'm curious how you're doing the mapping. Do you mean to say that the application does a mapping between a user's session when it gets created and the CAS Service Ticket, then invalidates the session when it gets the message from the CAS server? -Laura -- 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 -- 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
