WORKERS AHEAD!

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.

Configure Service Protocols

Applications registered with CAS that intend to use the CAS protocol are given the option to indicate their support for specific CAS protocol versions. If the service registration record declares support for specific CAS protocol versions, then attempts at validating service tickets using other CAS protocol versions would be blocked and should fail.

Usage

This feature specifically applies to CAS registered services applications.

By default and for backward compatibility reasons, if no supported protocols are specified for the service registration record then all CAS protocol versions are allowed.

A sample JSON file follows:

{
  "@class" : "org.apereo.cas.services.CasRegisteredService",
  "serviceId" : "^https://app.example.org.+",
  "name" : "App",
  "id" : 1,
  "supportedProtocols": [ "java.util.HashSet", ["CAS10", "CAS20"] ]
}

Accepted values are as follows:

Storage	Description
`SAML1`	See this guide.
`CAS10`	See this guide.
`CAS20`	See this guide.
`CAS30`	See this guide.