|title||New CAS documentation site|
CAS documentation has moved over to apereo.github.io/cas, starting with CAS version 4.x. The wiki will no longer be maintained. For the most recent version of the documentation, please refer to the aforementioned link.
The CAS User Manual is the primary source of documentation for implementers of the Jasig CAS server component.
New to CAS
For readers unfamiliar with CAS, the Overall Architecture section is a good starting point to learn what CAS is and how it works. Readers will learn that CAS is a multi-protocol SSO solution and they will want to review protocols to learn the use cases under which a particular protocol applies. Once review of background material is complete, readers should consider working through the CAS demonstration, which will provide a working product and an introduction to configuration.
CAS integrates with the following authentication mechanisms:
CAS uses tickets to implement supported authentication protocols, so it follows that ticket behavior determines most aspects of security policy. In its default configuration (as of CAS 3.3.3), CAS provides for the following:
CAS provides for high availability by placing client authenticated state data in tickets stored in a TicketRegistry component that has a number of implementations that support distributed environments:
|title||Default is Not Distributed|
The DefaultTicketRegistry, which is enabled by default, is not suitable for high availability environments unless combined with tool such as Terracotta.