> The guy before me was able to have the two use the same > SQL database as a ticket registry, appears using JBoss. I haven’t been able > to find documentation in the CAS user manual about that doing it that way.
Using a database for ticket storage is well supported, http://www.ja-sig.org/wiki/display/CASUM/JpaTicketRegistry. We use that here at Virginia Tech and have been pleased with performance and HA capability. > I would like to avoid multicasting if possible. You do not need need Tomcat session replication for HA setups in CAS. The only state you'd been replicating is for the initial login screen, and in the rare case that a node fails between the time the user first accesses the login form and submission time, he would just be presented with the login form again on another node. If this behavior is unacceptable, you could configure Spring WebFlow for session-less state management. Search the list archives for more info on that; we've discussed it recently. 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
