This post is not official yet and may be heavily edited as CAS development makes progress. Watch for further updates.
The blog is managed and hosted on GitHub. If you wish to update the contents of this post or if you have found an inaccuracy and wish to make corrections, we recommend that you please submit a pull request to this repository.
The official CAS
5.3.0 GA was released on June 29th, 2018. Since then, the project has been moving forward with development of the next feature release that is tagged as
6.0.0. Note that this is a major release of the CAS software which may present significant changes in architecture, configuration or behavior. Please review the release policy to learn more about the scope of the release.
This post intends to highlight some of the improvements and enhancements packed into the third release candidate in the
You can read about the previous release candidate here.
Shake Well Before Use
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 simply 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.
In order to start experimenting with release candidates, at any given time, you should be able to append
-SNAPSHOT to the CAS version specified in order to take advantage of snapshot builds as changes are made and published.
gradle.properties of the overlay, adjust the following setting:
- New & Noteworthy
- Small Stuff
- Library Upgrades
- Get Involved
New & Noteworthy
Extensive CouchDb support is now provided by CAS to handle storage concerns when it comes to authentication, audit and throttling, multifactor authentication, and more.
SAML2 IdP Single Logout
Basic functionality is now included to have CAS submit SAML2 logout requests to service providers, who currently have a registered session record with CAS.
- Delegated authentication is improved to execute the authentication step only once.
- Service access strategy SAML2 service providers and other service types can now handle the
- Radius authentication now attempts to also submit the client IP address to the radius server.
- Small fixes to the SAML2 callback url pattern.
- CAS internal Gradle build should continue working against IDEA
- SAML2 responses can optionally include a
SubjectConfirmationblocks, on a per-service basis.
- The background job responsible for cleaning trusted expired MFA records is now scheduled correctly on startup.
- Spring Boot
- Spring Boot Admin
- Person Directory
- Spring Data
- Spring Cloud
- Amazon SDK
- Spring Security
- Google Maps
- Start your CAS deployment today. Try out features and share feedback.
- Better yet, contribute patches.
- Suggest and apply documentation improvements.
Big thanks to all who participate in the development of this release to submit patches and contribute improvements. Keep’em coming!