On 11/09/2010 02:55 PM, Marvin Addison wrote: >> Have you suggestions to avoid this problem? > There is only one solution at present. Enable session affinity in > your load balancer so the user is always directed to the same node > containing servlet session-based flow state. I've had the same problem and figured out that also configuring session affinity on the loadbalancer also does not solve the problem entirely. Single-Sign-On works, but Single-Sign-Out still doesn't. If the CAS server talks back to the clustered application to tell it that it has been logged out, he of course does not have the session-cookie of the user and therefore might get redirected to the wrong instance. Session clustering also doesn't help in this case due to CAS-internal design apparently (and from what I've been told on this mailinglist here).
Scott: Is this something which you plan to look at for further releases? Best regards, Felix -- ----------------------------------------------------------------------- Felix Reinel | Web & Systems Administrator Office: D132 ESO | Tel.: +49-89-32006-171 | Address: Fax.: +49-89-32006-677 | European Southern Observatory Mobile: +49-160-2956856 | Karl-Schwarzschild-Strasse 2 E-Mail: [email protected] | D-85748 Garching bei Muenchen, Germany ----------------------------------------------------------------------- http://www.eso.org
signature.asc
Description: OpenPGP digital signature
