You are viewing the development documentation for the Apereo CAS server. The functionality presented here is not officially released yet. This is a work in progress and will be continually updated as development moves forward. You are most encouraged to test the changes presented.To view the documentation for a specific Apereo CAS server release, please choose an appropriate version. The release schedule is available here.
Servlet Container Configuration
A number of container options are available to deploy CAS. The WAR Overlay guide describes how to build and deploy CAS.
How Do I Choose?
There are is a wide range of servlet containers and servers on the menu. The selection criteria is outlined below:
- Choose a technology that you are most familiar with and have the skills and patience to troubleshoot, tune and scale for the win.
- Choose a technology that does not force your CAS configuration to be tied to any individual servers/nodes in the cluster, as this will present auto-scaling issues and manual effort.
- Choose a technology that works well with your network and firewall configuration and is performant and reliable enough based on your network topology.
- Choose a technology that shows promising results under your expected load, having run performance and stress tests.
- Choose a technology that does not depend on outside processes, systems and manual work as much as possible, is self-reliant and self contained.
All servlet containers presented here, embedded or otherwise, aim to be production ready. This means that CAS ships with useful defaults out of the box that may be overridden, if necessary and by default, CAS configures everything for you from development to production in today’s platforms. In terms of their production quality, there is almost no difference between using an embedded container vs. an external one.
Unless there are specific, technical and reasonable objections, choosing an embedded servlet container is almost always the better choice.
Please see this guide.
Please see this guide
CAS can be easily started as Unix/Linux services using either
systemd. To learn
more, please visit this guide.