Login SAML
SAML Assertion Consumer Service (ACS)
Endpoint the Identity Provider posts the SAMLResponse to (HTTP-POST
binding). Both IdP-initiated (no RelayState) and SP-initiated (the
RelayState issued by the initiate
endpoints) flows land here. On success, redirects to the connection’s
redirect URI with a challenge_token that can be finalized via
Finalize login.
This endpoint is called by the IdP, not by your application directly.
POST
SAML Assertion Consumer Service (ACS)
Path Parameters
The SAML provider identifier (okta or google).
Examples:
"okta"
"google"
The SAML connection identifier (prefixed with samlc_).
Example:
"samlc_01jqebhswje1ka1z7ahr9rfsgt"
Body
application/x-www-form-urlencoded
Response
Redirect to the connection's redirect URI with one of:
challenge_token=<jwt>— login may be finalized via the Finalize login endpoint.error=<code>&error_description=<message>— SAML validation or provisioning failure (e.g.saml_authentication_failed,saml_user_not_provisioned,saml_email_domain_not_allowed,email_already_in_use).
SAML Assertion Consumer Service (ACS)