Scott, I have a couple followup questions:
1. Is a load balancer set to use sticky-sesssion enough to meet this requirement or do I actually need to cluster the tomcat instances which host CAS? 2. Is the Ticket Registry part of CAS or part of the application that is being secured? Also if I wanted to add a suffix to the ticket were would this be done? Thanks, Pete On Oct 31, 2006, at 8:50 AM, Scott Battaglia wrote: > Pete, > > There are two parts of CAS that can be load balanced/clustered. > The first part is the authentication part where you merely need to > cluster Tomcat so that the user can always find their "login flow". > > The second part is the Ticket Registry itself. Ticket Registries > either need to be clustered (through something such as our > JBossTicketRegistry) or you need to somehow route the request to > the specific ticket registry (this can be accomplished via > appending a suffix to each ticket id and then using the load > balancer to determine which machine that ticket belongs to). > The 3.1 release of CAS will include a JBossTicketRegistry. > > -Scott > > On 10/31/06, Peter Giesin < [EMAIL PROTECTED]> wrote:All of > the docs talk about the need to cluster CAS servers if they > are in a load balanced environment. Is this a custom solution, or is > it already built into the code? I have CAS running on 4 load balanced > tomcat servers. Is clustering Tomcat enough? Or do I need to > customize the CAS code. > > Thanks, > Pete > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
