History

amit2103 f2128ad054 Bael 5249 cleanup (#4108 ) * Added parent module on poms that have no parent defined * Removed dependency reduced pom from undertow module * [BAEL-5249] - 21.02 - pom cleanup - formatted pom.xml		2018-04-26 14:37:47 +02:00
..
etc/cas/config	Refactor Cas-Server Configurations (#2970 )	2017-11-06 22:23:20 +01:00
maven	Refactor CAS Modules into CAS (#2916 )	2017-10-30 15:45:16 +01:00
src/main/resources	Added SQL File to Create test Database (#3086 )	2017-11-22 23:22:34 +01:00
.gitignore	Refactor CAS Modules into CAS (#2916 )	2017-10-30 15:45:16 +01:00
LICENSE.txt	Refactor CAS Modules into CAS (#2916 )	2017-10-30 15:45:16 +01:00
README.md	Refactor CAS Modules into CAS (#2916 )	2017-10-30 15:45:16 +01:00
build.cmd	Refactor CAS Modules into CAS (#2916 )	2017-10-30 15:45:16 +01:00
build.sh	Refactor CAS Modules into CAS (#2916 )	2017-10-30 15:45:16 +01:00
mvnw	Refactor CAS Modules into CAS (#2916 )	2017-10-30 15:45:16 +01:00
mvnw.bat	Refactor CAS Modules into CAS (#2916 )	2017-10-30 15:45:16 +01:00
pom.xml	Bael 5249 cleanup (#4108 )	2018-04-26 14:37:47 +02:00

README.md

CAS Overlay Template

Generic CAS WAR overlay to exercise the latest versions of CAS. This overlay could be freely used as a starting template for local CAS war overlays. The CAS services management overlay is available here.

Versions

<cas.version>5.1.x</cas.version>

Requirements

JDK 1.8+

Configuration

The etc directory contains the configuration files and directories that need to be copied to /etc/cas/config.

Build

To see what commands are available to the build script, run:

./build.sh help

To package the final web application, run:

./build.sh package

To update SNAPSHOT versions run:

./build.sh package -U

Deployment

Create a keystore file thekeystore under /etc/cas. Use the password changeit for both the keystore and the key/certificate entries.
Ensure the keystore is loaded up with keys and certificates of the server.

On a successful deployment via the following methods, CAS will be available at:

http://cas.server.name:8080/cas
https://cas.server.name:8443/cas

Executable WAR

Run the CAS web application as an executable WAR.

./build.sh run

Spring Boot

Run the CAS web application as an executable WAR via Spring Boot. This is most useful during development and testing.

./build.sh bootrun

Warning!

Be careful with this method of deployment. bootRun is not designed to work with already executable WAR artifacts such that CAS server web application. YMMV. Today, uses of this mode ONLY work when there is NO OTHER dependency added to the build script and the cas-server-webapp is the only present module. See this issue and this issue for more info.

Spring Boot App Server Selection

There is an app.server property in the pom.xml that can be used to select a spring boot application server. It defaults to "-tomcat" but "-jetty" and "-undertow" are supported. It can also be set to an empty value (nothing) if you want to deploy CAS to an external application server of your choice and you don't want the spring boot libraries included.

<app.server>-tomcat<app.server>

Windows Build

If you are building on windows, try build.cmd instead of build.sh. Arguments are similar but for usage, run:

build.cmd help

External

Deploy resultant target/cas.war to a servlet container of choice.