CAS 6.1.0 RC2 Feature Release

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 6.0.0 GA was released on December 28th, 2018. Since then, the project has been moving forward with development of the next feature release that is tagged as 6.1.0. 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 second release candidate in the 6.1.0 series.

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.


In the of the overlay, adjust the following setting:

System Requirements
There are no changes to the minimum system/platform requirements for this release.


New & Noteworthy

SAML2 Attribute Value Types

Attribute values put into a SAML2 response can now carry specific type information if necessary on a per-service basis. Complex attribute values that are formatted as POJO objects are conditionally serialized into their XML representation using Jackson’s XmlMapper.

See this for more info.

OAuth2 JWT Access Tokens

OAuth or OpenID Connect Access tokens can now be produced as JWTs on a per-service basis.

Groovy Acceptable Usage Policy

Handling acceptable usage policy decisions can now be managed using a Groovy script.

OpenID Connect WebFinger

Support for OpenID Connect WebFinger Issuer Discovery is now available.

Cassandra Ticket Registry

As yet another storage option, CAS tickets can now be stored in Apache Cassandra.

Redis Audit Manager

As yet another storage option, CAS audit logs can now be stored in Redis.

Other Stuff

  • Small improvements affect multifactor authentication bypass during validation events.
  • Health indicators, that report status to the health actuator endpoint, can be conditionally enabled via CAS settings.
  • The process of publishing and releasing CAS has switched to use the maven-publishing Gradle plugin.
  • The status actuator endpoint is able to operate partially without the presence of the health actuator endpoint.
  • Fixes to OAuth2 claim release, honoring the attribute release policy for relying parties.
  • Continued effort to ensure CAS unit/integration tests are upgraded to use the JUnit 5 framework.
  • Minor documentation fixes regarding Redis-related properties.
  • Small fixes related to triggering multifactor authentication based on principal attributes.
  • Attribute release policies for OpenID Connect relying parties can operate without a defined scope.
  • Adjustments to dependency management to ensure the CAS overlay and the command-line shell remain functional.
  • CAS audit managers may only record a selection of audit actions, configured in CAS settings.
  • Audit logs for OAuth user profile requests attempt to record client identifiers and recipients better.
  • A new actuator endpoint is available to report back on the availability of Duo Security using its ping API.

Library Upgrades

  • Gradle
  • Ribbon
  • Apache HttpClient
  • Mockito
  • Nimbus
  • Spring Boot
  • Spring Security
  • Spring Session
  • Spring Boot Admin
  • Apache jClouds
  • JUnit
  • Lombok
  • Twillio
  • BouncyCastle
  • Apache Tomcat
  • MongoDB Driver
  • MYSQL Driver
  • Slf4j
  • MariaDB Driver
  • MSSQL Driver
  • Byte-Buddy


Get Involved


Big thanks to all who participate in the development of this release to submit patches and contribute improvements. Keep’em coming!

Misagh Moayyed

Related Posts

Apereo CAS as an OAuth2 Authorization Server

Learn how to configure CAS as an OAuth2 Authorization Server and configure Spring Boot client app to work with it

Apereo CAS - SAML2 Identity Provider Integration w/ Gitlab (also staring HAProxy and LDAP)

Learn how Apereo CAS may act as a SAML2 identity provider for Gitlab and run everything locally on a workstation with Docker and Java.

Apereo CAS - Keeping Healthy with Spring Boot

Learn how you may keep your Apereo CAS deployment healthy, monitoring its status using Spring Boot actuator endpoints and health indicators.

CAS 6.1.0 RC1 Feature Release which I present an overview of CAS 6.1.0 RC1 release.

Apereo CAS - SAML2 Identity Provider Integration w/ InCommon

Learn how Apereo CAS may act as a SAML2 identity provider to integrate with service providers from metadata aggregates such as InCommon with various attribute release policies for research and scholarship, etc.

CAS 6.1.x Deployment - WAR Overlays

Learn how to configure and build your own CAS deployment via the WAR overlay method, get rich quickly, stay healthy indefinitely and respect family and friends in a few very easy steps.

Apereo CAS - Have you been pawned?

Learn how Apereo CAS may be configured to check for pawned passwords and warn the user, using the service

Apereo CAS - OohLala Mobile SAML2 Integration

Learn how to integrate OohLala Mobile with Apereo CAS running as a SAML2 identity provider.

Apereo CAS - Cranium Cafe SAML2 Integration

Learn how to integrate Cranium Cafe with Apereo CAS running as a SAML2 identity provider.

Apereo CAS - eLumen SAML2 Integration

Learn how to integrate eLumen with Apereo CAS running as a SAML2 identity provider.