Frank, Did you set up session replication on the CAS nodes? If the proxy is not doing simple failover (which seems to be the case), then the node that didn't service your initial login will ignore that login since it hasn't seen your session before, thus kicking you back to the login page.
Others will have more authoritative answers. Best regards, -- Carlos. -----Original Message----- From: Frank Van Damme [mailto:[email protected]] Sent: Thursday, 05 July, 2012 10:02 To: [email protected] Subject: [cas-user] reverse proxy & load balancing behind Apache 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? -- Frank Van Damme No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author. -- 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
