SsoTestSignInResponseDto
Example
{ "id": "string", "connection_id": "string", "environment_id": "string", "type": "saml", "status": "pending", "start_url": "string", "started_at": "2026-04-20T12:00:00.000Z", "expires_at": "2026-04-20T12:00:00.000Z", "outcome": "success", "reason": "string", "email": "string", "first_name": "string", "last_name": "string", "federated_subject_id": "string", "amr": [ "string" ], "domain_outcome": "accepted", "completed_at": "2026-04-20T12:00:00.000Z" }
Properties
Open in a browser to run the round-trip. Valid until `expires_at`, and only while the test is pending.
Why the test failed, in the sign-in error vocabulary. The provider refused the sign-in (`provider_rejected`); the response did not verify against the connection's certificate (`signature_invalid`), fell outside its validity window (`assertion_expired`), named a different audience (`audience_mismatch`) or a different issuer (`issuer_mismatch`), or could not be verified for another reason (`assertion_invalid`); it had already been used (`assertion_replayed`); a required attribute was absent (`attribute_missing`); the email's domain is not verified for the organization (`email_domain_not_allowed`); or the round trip failed some other way (`sso_error`).
How the asserted email's domain fared against the bound organization's verified claims. `no_boundary` when the connection is bound to no organization in the Environment.
Tell us how we can improve this guide.