Just the login phase requires affinity (and only if you don't use any form of session clustering, which most people don't). You can cluster the backend via a variety of methods.
On Thu, Apr 21, 2011 at 8:56 PM, Romeo Theriault <[email protected]>wrote: > On Thu, Apr 21, 2011 at 11:48, Marvin Addison <[email protected]>wrote: > >> > Note that CAS 3.4.7 fails behind a load balancer if you're not using >> sticky >> > sessions but using clustered sessions (its because each server has its >> own >> > key). >> > Marvin's put in a fix to not have to use keys and I'll be cutting the >> > release later. >> >> It's important to note that my fix would still require session >> affinity since the random component of the flow key is stored in >> Webflow conversation state. > > > Which part of the communication flow requires the affinity? The client > webbrowser or the Service Validation? It doesn't seem that you can guarantee > that both go to the same backend server. > > Thanks for the clarification, we're just starting to get ready for a portal > rollout at our University and are planning to cluster CAS with Terracotta > behind some LB's for the authentication. > > > >> The requirement for session affinity, >> however, is nothing new. When SWF finally re-introduces sessionless >> flows, we can document how to do configure CAS for a non-sticky setup. >> Until then, sticky is a requirement for clustered CAS. >> >> 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 >> > > > > -- > Romeo Theriault > > > -- > 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
