Configuring Service Response Type

By default, authentication requests are handled with a browser redirect (i.e. 302) back to the calling application with the relevant parameters built into the url. This behavior can be optionally adjusted on a per-service basis to dictate other options when responding to services.

:information_source: Usage

This feature specifically applies to applications that understand and use the CAS protocol.

A sample JSON file follows:



1
2
3
4
5
6
7



{
  "@class" : "org.apereo.cas.services.CasRegisteredService",
  "serviceId" : "^https://.+",
  "name" : "sample service",
  "id" : 100,
  "responseType": "HEADER"
}

Accepted response types are as follows:

Parameter Description
REDIRECT This is the default option, where a browser 302 redirect navigates the user back to the calling application.
POST Same as above, except that parameters are POSTed back to the calling application.
HEADER Parameters constructed for this authentication request are inserted into the HTTP response as headers