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. To view the documentation for a specific Apereo CAS server release, please choose an appropriate version. The release schedule is also available here.
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.
A sample JSON file follows:
1
2
3
4
5
6
7
{
"@class" : "org.apereo.cas.services.RegexRegisteredService",
"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 |