> My understanding is when CAS is used in a load balanced environment... > it is mandatory to have CAS clustered as described in > https://wiki.jasig.org/display/CASUM/Clustering+CAS
You don't have to use JBossCacheTicketRegistry for the ticket registry, but the points of consideration in that page are correct. You should think about all of them. Other alternatives for a ticket registry suitable for HA environments: - JpaTicketRegistry - MemcachedTicketRegistry > Since CAS stores > everything thing is the session is not enough to have the Tomcat's session > replicated ? Your premise is incorrect. Under most circumstances CAS stores minimal information in the session. The DefaultTicketRegistry stores data in a ConcurrentHashMap which has no relation to the Tomcat container session. You need to use one of the TicketRegistry implementations I mentioned above. I would say the memcached solution is the easiest to stand up if you don't have an existing database, otherwise JPA. Clustering Tomcat will provide durability for the login process, but I would argue that the value is not worth the effort. If a node fails during login, the worst that happens is the user is shifted to a new node and loses login state. That's no big deal in our view and we don't both with the additional complexity. 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
