All, We've had our CAS 3.4.10 installation up now for approx. 8 months and all has been working perfectly. We are currently on a 1 node installation using a Tomcat 7 w/ MySQL as the datastore for the Ticket Registry on RHEL 6.3 x86_64 (VM on Vmware 3.5). We are looking to make this an Highly Available CAS implementation currently and I've noticed that a great deal of progress seems to have been made in this area since the release of 3.5 and the implementation of EhCache. With this said, I'm curious how difficult is it to move from 3.4.10 to 3.5? Are there any major configuration changes to the deployerConfigContext.xml with regards to how AD authentication is handeled? Many thanks for your help on this matter.
Ben Branch UNIX/Linux Administrator University of Central Oklahoma ITIL Foundation v3, Network+, RHCSA 100 N. University Drive, Box 122 Edmond, OK 73034 D: 405.974.2649 | M: 405.550.6804 | bbranch@uco.<mailto:bbranch@uco.>edu | www.uco.edu<http://www.uco.edu/> "If you wish to know your past, look at your present conditions. If you wish to know your future, look at your present actions." - Siddhartha Gautama **Bronze+Blue=Green** The University of Central Oklahoma is Bronze, Blue, and Green! Please print this e-mail only if absolutely necessary! **CONFIDENTIALITY** This e-mail (including any attachments) may contain confidential, proprietary and privileged information. Any unauthorized disclosure or use of this information is prohibited. -- 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
