Bootiful CAS 5 Overlay


Overview

As you may know, the recommended strategy to start a CAS deployment today is via the WAR Overlay Installation Method. The idea is that a deployment gets to keep only local customizations and inherits everything else from a pre-built pre-configured instance. Not only this allows one to keep track of intentional changes, but also makes it easier to upgrade the software in place by simply bumping the CAS version in the overlay script.

CAS 5 itself is entirely based on Spring Boot. Today, CAS 5 overlays for both Maven and Gradle too are modified to accommodate easier deployment options via Spring Boot.

Here’s how.

Bootiful Overlay

Today, adopters are given 3 choices to deploy an overlay:

  1. Run the CAS web application as an executable WAR via a java -jar <cas-war-file> type of command.
  2. Deploy the <cas-war-file> into an external container of choice, such as Apache Tomcat.
  3. [NEW] Run the CAS web application as an executable WAR via the Spring Boot’s Maven/Gradle plugin, though you may be interested in this issue.

The 3rd option is similar to the native java -jar ... command with the main difference that the Spring Boot plugin is able to recognize the presence of Spring Boot’s devtools that is shipped with CAS by default and allows for ad-hoc live monitoring of CAS resources.

This is specially helpful perhaps during UI design; such that you could keep modifying html, css, and js resources and CAS will auto-detect changes and allows you to see them via a simple refresh of your browser.

Lots quicker!

Misagh Moayyed

Related Posts

CAS 6.0.0 RC3 Feature Release

...in which I present an overview of CAS 6.0.0 RC3 release.

Apereo CAS - Multifactor Authentication with RADIUS

Learn how Apereo CAS may be configured to trigger multifactor authentication using a RADIUS server and its support for the Access-Challenge response type.

CAS Vulnerability Disclosure

Disclosure of a security issue with the MFA features.

CAS 6.0.0 RC2 Feature Release

...in which I present an overview of CAS 6.0.0 RC2 release.

Apereo CAS - dotCMS SAML2 Integration

Learn how to integrate dotCMS, a Content Management System and Headless CMS, with Apereo CAS running as a SAML2 identity provider.

Effective Software Troubleshooting Tactics

A collection of what hopefully are obvious troubleshooting tactics when it comes to diagnosing software deployment issues and configuration problems.

Apereo CAS - MaxMind Geo2IP ISP Integration

Learn how you may determine the Internet Service Provider, organization name, and autonomous system organization and number associated with the user's IP address in CAS using MaxMind services and present warnings in the authentication flow for the end-user if an IP address is matched.

Notes from Better by Design 2018

Be interested in humans and human success.

Apereo CAS - Authentication Lifecycle Phases

Tap into the Apereo CAS authentication engine from outside, and design extensions that prevent an unsuccessful authentication attempt or warn the user after-the-fact based on specific policies of your choosing.

CAS 6.0.0 RC1 Feature Release

...in which I present an overview of CAS 6.0.0 RC1 release.