On Thu, Nov 11, 2010 at 6:39 AM, Alexander Mills <[email protected]> wrote: > Hey > > I am looking into CAS clustering or high availability - and was interested > to learn that clustering/HA in Tomcat is... not an easy task
I've heard things have improved in TC6/7. In any case I would argue container session clustering isn't worth the effort in CAS. > - due to ticket caches being stored in a servlet context. This is simply the default configuration; the DefaultTicketRegistry component is neither designed nor recommended for HA setups. > And so I was interested to learn about placing an RDBMS between the > loadbalancer and CAS to try and avoid ticket replication issues, and > authentication failing due to ticket validation being sent to a different > node than the ticket granting node. > > References: http://tp.its.yale.edu/pipermail/cas/2004-June/000504.html You're citing a thread from over 6 years ago that is irrelevant for current CAS server versions. The following ticket storage mechanisms are available for HA setups: - https://wiki.jasig.org/display/CASUM/JpaTicketRegistry - https://wiki.jasig.org/display/CASUM/JBOSS+TreeCache - https://wiki.jasig.org/display/CASUM/MemcacheTicketRegistry The JBoss Cache solution is discussed in further detail at https://wiki.jasig.org/display/CASUM/Clustering+CAS. Choose the technology for which you have resources and expertise. We use JPA here and it's worked well for us. M -- 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
