CAS Community, We're pleased to announce the CAS 3.2 RC4 release. If you're wondering if you missed RC1 - RC3, let's just say that it helps if you do your own internal testing before you tag stuff, not after. So let's just call RC1 - RC3, internal RCs ;-)
So what's new in CAS 3.2 RC4? Updated dependencies: Log4j, Spring 2.5.1, Acegi Security 1.0.6, Spring LDAP, Spring Web Flow Bug Fixes: SPNEGO fixes, check ServiceManager enabled/disabled flag, Service Theme Resolver support for emtpy theme names, Enhancements: UTF-8 as the default in the PasswordEncoder, filtering for domain controllers in NtlmHandler. Single Sign Out supports timeouts, ability to enable/disable SSout New Features: Hard Timeout Expiration policy, updated Spring configuration so that you can drop a file in a specific directory and have it loaded automatically, Inspektr auditing tool If you're wondering why we went from CAS 3.1.2 to CAS 3.2, we felt that the changes to the configuration method and the addition of the new Inspektr tool (Note: it replaces the event handler example code, which was not considered production code. Inspektr is considered a production codebase) sufficiently differentiated it from the CAS 3.1.x branch. You can download the files from here: http://www.jasig.org/products/cas/downloads/ or http://www.jasig.org/downloads/cas/ (if the site isn't updated yet) Please provide any feedback (good, bad, or indifferent). Again, the changes in the configuration as well as the usage of the Inspektr tool for auditing are relatively major changes, so anyone upgrading from CAS 3.1.1 to CAS 3.2should be aware of this. Thanks -Scott -- -Scott Battaglia LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
