By default all CAS clients store their information that determines if you authenticated or not into the session. The easiest thing is to merely replicate the session, if possible.
Otherwise, you'd need a custom client to store the "we've authenticated" information somewhere else and be able to find it. -Scott On Sun, Feb 8, 2009 at 4:32 AM, sol myr <[email protected]> wrote: > Hi, > > We are currently evaluating CAS for single sign on, and are especially > interested in clustering ( load balancing and failover). > > We saw some great wiki documentation on clustering the *CAS server* itself. > However, we are still looking for documentation on clustering our > *business* applications (the ones to be protected by CAS SSO). > I.e: say we a business applications (JEE - web and EJBs) which is currently > clustered, with some data replication, running behind some load balancer. If > we want to "cassify" it (make users login through CAS) - do we need to take > any special steps, especially for *clustered* applications? > > Is there any documentation for this ? > > Thanks very much. > > -- > 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
