I am trying to set up CAS in a WebLogic cluster so that if the primary server goes down for any reason, the secondary server(s) would take over. And ideally, the backup server would pick up where the primary server left off, making the primary server's failure transparent to the user.
I have run into a problem and would appreciate help. Basically, I'd like to know if CAS places service tickets (and other data needed for failover) in session memory. Can anyone confirm this? I have CAS deployed to a WebLogic cluster consisting of two managed servers. The cluster is accessed through an Apache http proxy server. I have changed CAS's weblogic.xml configuration file to specify in-memory session replication. All works fine when only one managed server is used throughout the CAS authentication process. However, when the protected web application goes back to CAS through the proxy to redeem a service ticket, and the other managed server is used, that server has no record of the service ticket (which was issued by the other managed server). So, I want to make sure that the service ticket is being stored in session memory. If so, then the problem would be a WebLogic session replication issue, not a CAS issue. Any help would be much appreciated! Thanks, Barry Silk -- 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
