We currently have CAS running across multiple Tomcat servers using MySQL as the backend DB for both Ticket & Service registries. I'm looking at implementing 3.5.1 and removing the dependency on the MySQL DB server (as it's not clustered). It looks like I have a few options to pull this off.
For Ticket Registry I'm looking into ehcache, as it looks like the 'simplest' to implement. For Service Registry I'm primarily looking at LdapServiceRegistryDao - we already have a robust LDAP infrastructure with multiple masters & replicas in place. Googling this I really can't find much information on implementing it. Most of the email chatter ended in 2009. Is anyone using this for their Service Registry? If so, are you 'happy' with it? Are there any examples for the LDAP Schema, I was able to find one here https://issues.jasig.org/browse/CAS-580 date June 2009. Assuming a common LDAP pool, will all the CAS servers reload the list of services when there is an update to it? (I seem to remember an email thread about that not happening, years ago). The other option is the JsonServiceRegistryDao, which looks interesting, and, passing the updated file around wouldn't be a big deal - the only issue is that I would need to edit the file, as opposed to using some sort of web interface to add/remove services, not a big deal for me, but, I really don't want to login from a Cruise ship when I'm on vacation :) Any other suggestions would be appreciated as well. Thanks, Chris Peck College of William and Mary Williamsburg, VA -- 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
