Skip to content
Dashboard
Theme
Theme

IdP-initiated sign-in

Enable unsolicited SAML with broker confirmation and a short handoff into your application's PKCE flow.

View Markdown

IdP-initiated SAML is off by default on each connection. Enabling or changing it requires Business or Enterprise, a live environment-scoped publishable client key and an exact registered default redirect URI. Disabling removes that binding. Existing enabled settings remain enforced after a plan downgrade.

Only genuinely absent or empty RelayState enters this flow. An invalid native, test, compatibility or forwarded state never falls back to unsolicited sign-in. The broker verifies the assertion and durable replay protection before showing confirmation; an unsolicited assertion must have no InResponseTo and its signed age must be between zero and 120 seconds.

The broker displays the application, organization and a masked account. There is no skip-confirmation option. Continue is a POST protected by exact Origin and arrival-host checks, a cookie-bound CSRF token and a Secure, HttpOnly, SameSite=Lax broker cookie. Confirmation lasts at most 120 seconds; Cancel or timeout records an abandoned sign-in attempt.

Continue redirects to the configured application URI with an opaque handoff query parameter. This ticket is single use, lasts at most 60 seconds and is bound to the environment, connection, registered redirect and broker cookie. It is not an authorization code or an access token.

Your application starts its normal native /sso/authorize request using the live publishable client, exact registered redirect, fresh application state and its own S256 PKCE challenge, and includes the received handoff. Return to the same primary, standby or supported custom broker host that owns the confirmation cookie. The handoff does not replace normal client, redirect, state or PKCE validation.

After successful authorization, exchange the ordinary native code using its matching verifier. Never send the handoff to the token endpoint. Do not log the ticket, put it in diagnostics or treat the confirmed email as authority to merge an existing account.

Sign-in policies are checked against current authority. Missing replay authority, invalid bindings, expired tickets or changed eligibility refuse the flow. See sign-in policies and profiles for application-side identity and session boundaries.