ACS: consume the signed assertion and issue a session. Returns the token pair (a browser deployment would instead set the refresh cookie and redirect to RelayState).
POST
End-user session operationId: acs/v1/auth/saml/{application_id}/{connection_id}/acs Authorization
Called from the browser with the publishable application id (x-application-id); the access token lives in memory.
Path parameters
application_idstring<uuid> requiredApplication id
connection_idstring<uuid> requiredConnection id
Request body · required
RelayStatestringSAMLResponsestring required
Responses
200 Session issued
{
"data": {
"aal": 0,
"access_token": "string",
"expires_in": 0,
"refresh_token": "string",
"session_id": "018f3c4a-7b2e-7c1d-9e0a-1f2b3c4d5e6f",
"token_type": "string"
},
"error": {
"code": "string",
"message": "string"
},
"meta": {
"timestamp": "string"
},
"success": false
} 401 Assertion rejected
Request
curl -X POST "http://localhost:8080/v1/auth/saml/018f3c4a-7b2e-7c1d-9e0a-1f2b3c4d5e6f/018f3c4a-7b2e-7c1d-9e0a-1f2b3c4d5e6f/acs" \
-H "Content-Type: application/json" \
-d '{
"RelayState": "string",
"SAMLResponse": "string"
}'Try it
live requestPOST
http://localhost:8080/v1/auth/saml/018f3c4a-7b2e-7c1d-9e0a-1f2b3c4d5e6f/018f3c4a-7b2e-7c1d-9e0a-1f2b3c4d5e6f/acs