Check out https://wiki.jasig.org/display/CASUM/Clustering+CAS if you really must preserve application login state as well.
Brian On Thu, Jul 5, 2012 at 11:22 AM, Philippe MARASSE < [email protected]> wrote: > Member ;-), > > As far as I remember, clustering is not so easy. I've set up a few years > ago a clustered CAS involving a few more steps : > 1 - Clustering tomcat (on-line documentation at apache site is good > enough) > 2 - Make CAS redistributable in web.xml > 3 - Share the tickets registries (JPATicketRegistry if I'm not mistaken) > 4 - Use sticky sessions in the balancer > > Rdgs > > Le 05/07/2012 16:02, Frank Van Damme a écrit : > > List, >> >> I'm having a small shenanigan w.r.t. putting Cas behind a reverse >> proxy/load balancer running Apache (I'm sorry if this is slightly off >> topic). >> >> The good news is that it's extremely easy to configure a load balancer >> with Apache. >> >> ProxyPass /cas balancer://casstuff/ >> <Proxy balancer://casstuff> >> BalancerMember ajp://3.3.3.10:8009/cas >> BalancerMember ajp://3.3.3.11:8009/cas >> </Proxy> >> >> ... and that's it. logging in and out works (the ticket store is >> shared with jpaTicketRegistry). Only, when logging out and then >> logging in again, I get a http 302 and am redirected to /cas/login. >> So, I just get the login dialog again. I can get around it by >> refreshing the page and trying to log in again, which works as >> expected. >> >> If I remove one of the BalancerMember, the setup works as expected. Any >> ideas? >> >> > > -- > Philippe MARASSE > > Service Informatique - Centre Hospitalier Henri Laborit > BP 587 - 370 avenue Jacques Coeur > 86021 Poitiers Cedex > Tel : 05.49.44.57.19 > > > -- 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
