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.
etc directory contains the configuration files and directories that need to be copied to
To see what commands are available to the build script, run:
To package the final web application, run:
SNAPSHOT versions run:
./build.sh package -U
/etc/cas. Use the password
changeitfor both the keystore and the key/certificate entries.
On a successful deployment via the following methods, CAS will be available at:
Run the CAS web application as an executable WAR.
Run the CAS web application as an executable WAR via Spring Boot. This is most useful during development and testing.
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 for more info.
There is an app.server property in the
pom.xml that can be used to select a spring boot application server.
It defaults to
-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.
If you are building on windows, try
build.cmd instead of
build.sh. Arguments are similar but for usage, run:
target/cas.war to a servlet container of choice.
Invokes the CAS Command Line Shell. For a list of commands either use no arguments or use
-h. To enter the interactive shell use