Step 2 is required for load balancing without a frontal load balancer which handles sticky sessions in front (the login webflow is using tomcat session)
In case of a simple failover, this step is not mandatory. Regards, -Arnaud On Wed, Mar 5, 2008 at 9:49 AM, Ina Müller <[EMAIL PROTECTED]> wrote: > Hello, > > we want to use CAS in a HA solution, so I had a look at > http://www.ja-sig.org/wiki/display/CASUM/Clustering+CAS. > > It describes three steps: > 1.- Ticket Uniqueness > 2.- Tomcat Session Replication > 3.- Ticket Cache Replication > > Steps 1 and 3 are clear. But for what scenario do I need step 2? > What CAS specific stuff in session state has to be replicated? > Isn't it enough to distribute the TGTs among the CAS servers to have a > failover solution? > > Or lets restate the question: if I omit step 2, what can go wrong in case > of failover to another server? > > Thank you for your help, Ina > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > -- Arnaud Lesueur LinkedIn: http://www.linkedin.com/in/lesueur
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
