My systems administrators here at UC Merced are wondering if anyone has done CAS load balancing behind F5. If any of you have any information that I can relay to them regarding your approach/configuration.
I don't believe there's anything in particular about F5 hardware with respect to how you would handle CAS application load balancing generally. The simplest solution in most cases is to go with a shared ticket registry (e.g. Ehcache or memcached) and configure the pool with session affinity (sticky sessions). The only loss of state would occur when a node is lost during the authentication process, which is a narrow enough window not to care about. If you do care about that you would need to implement session replication or implement client-side Webflow state [1].
M [1] https://github.com/serac/spring-webflow-client-repo -- 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
