Go to file

Misagh Moayyed 7da2ab3f71 working on overlay		2018-07-30 16:59:01 +04:30
etc/cas/config	merge maven and gradle overlays	2018-07-30 12:26:59 +04:30
gradle-overlay	working on overlay	2018-07-30 16:59:01 +04:30
maven-overlay	working on overlay	2018-07-30 16:59:01 +04:30
.gitignore	working on external tomcat setup	2018-07-29 15:18:20 +04:30
LICENSE.txt	Added Apache v2 license	2014-06-27 12:31:38 -04:00
README.md	merge maven and gradle overlays	2018-07-30 12:26:59 +04:30
apache-tomcat.zip	working on overlay	2018-07-30 16:59:01 +04:30
build.properties	working on overlay	2018-07-30 16:59:01 +04:30
build.sh	working on overlay	2018-07-30 16:59:01 +04:30

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>6.0.x</cas.version>

Requirements

JDK 11

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

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

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 the binary web application file cas.war after a successful build to a servlet container of choice.