Thanks Eric, I'll check it out. We have the same info in our MySQL DB, so this looks pretty handy. -chris
On Oct 15, 2012, at 3:20 PM, Eric Pierce <[email protected]> wrote: I've got a command-line editor for the JSON-based server registry file here: https://github.com/epierce/cas-json-tool It has support for pre- and post-run commands for revision control and distributing updated files to other cluster members and can add/modify extra attributes not supported by the web interface. We used to keep metadata (contact name, phone, etc) in the description field when using MySQL as the backend, but the data was never easily parseable. Now we're storing custom attributes in the JSON for contactName, contactEmail, etc and since cas-json-tool can require specific attributes, I can be sure all the needed info is captured when someone adds a new service. Any feedback on cas-json-tool is welcome. I've been using it here for a couple of months now and it's worked well, but it can always use more testers. -Eric On Mon, Oct 15, 2012 at 2:04 PM, Chris Peck <[email protected]> wrote: 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 -- Eric Pierce Identity Management Architect Information Technology University of South Florida (813) 974-8868 -- [email protected] -- 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 -- 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
