Servlet Container Configuration
A number of container options are available to deploy CAS. The WAR Overlay guide describes how to build and deploy CAS. To see the relevant list of CAS properties, please review this guide.
Embedded
Note that CAS itself ships with an embedded Tomcat container that allows the platform to be self contained as much as possible. You DO NOT need to configure and deploy to an externally configured container.
Remember that mostly all aspects of the embedded container can be controlled via the CAS properties. See this guide for more info.
Other embedded containers such as Jetty and Undertow may also be configured as a Tomcat replacement. To do this, the provided
Tomcat dependency MUST be excluded from the final package and substituted with either
spring-boot-starter-undertow or spring-boot-starter-jetty instead.
External
Optionally a CAS deployment may be deployed to any number of external servlet containers. The container MUST support
the servlet specification v3.1.x at a minimum.
At this time, Apache Tomcat 9 is NOT supported.
While there is no official project support, the following containers should be compatible with a CAS deployment:
Refer to the servlet container’s own documentation for more info.
Async Support
In the event that an external container is used, you must ensure it’s configured correctly to support asynchronous requests.
This is typically handled by setting <async-supported>true</async-supported> inside the container’s main web.xml file.
Docker
You may also be interested to deploy CAS via Docker. See this guide for more info.