58 lines
1.4 KiB
Markdown
58 lines
1.4 KiB
Markdown
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](https://github.com/apereo/cas-services-management-overlay).
|
|
|
|
# Versions
|
|
|
|
```xml
|
|
<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:
|
|
|
|
```bash
|
|
./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.
|
|
|
|
```bash
|
|
./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.
|
|
|