RC5 Release Notes

We strongly recommend that you take advantage of the release candidates as they come out. Waiting for a GA release is only going to set you up for unpleasant surprises. A GA is a tag and nothing more. Note that CAS releases are strictly time-based releases; they are not scheduled or based on specific benchmarks, statistics or completion of features. To gain confidence in a particular release, it is strongly recommended that you start early by experimenting with release candidates and/or follow-up snapshots.

Apereo Membership

If you benefit from Apereo CAS as free and open-source software, we invite you to join the Apereo Foundation and financially support the project at a capacity that best suits your deployment. Note that all development activity is performed almost exclusively on a voluntary basis with no expectations, commitments or strings attached. Having the financial means to better sustain engineering activities will allow the developer community to allocate dedicated and committed time for long-term support, maintenance and release planning, especially when it comes to addressing critical and security issues in a timely manner. Funding will ensure support for the software you rely on and you gain an advantage and say in the way Apereo, and the CAS project at that, runs and operates. If you consider your CAS deployment to be a critical part of the identity and access management ecosystem, this is a viable option to consider.

Get Involved

Resources

Overlay

In the gradle.properties of the CAS WAR Overlay, adjust the following setting:

1
cas.version=6.6.0-RC5
System Requirements
There are no changes to the minimum system/platform requirements for this release.

New & Noteworthy

The following items are new improvements and enhancements presented in this release.

Refreshable JDBC/JPA Integrations

CAS modules that offer an integration with a relational database, such as JPA Service Registry, are now extensively enhanced and tested to ensure the underlying components can correctly respond to refresh events, when the application context is reloaded once a property is changed.

Other Stuff

  • The configuration for the embedded Apache Tomcat is now allowed to create multiple connectors and ports. The secure and scheme attributes are also customizable.
  • Rules for redirecting to a service after a logout operation are now tightened to make sure protocol cross-over is not possible.
  • The OpenID Connect userinfo endpoint is now able to correctly process mapped claims defined in CAS configuration.

Library Upgrades

  • Spring Security
  • Google Firebase
  • Spring Data
  • Spring Boot
  • Spring Integration
  • Dropwizard
  • Gradle
  • Amazon SDK
  • Okio