Skip to content
Dashboard
Theme
Theme

Sign-in flow visualizer

Step through SP-initiated SAML, IdP-initiated SAML and the OIDC code flow hop by hop, with the checks that run at each step.

View Markdown

Pick a flow, then use Next and Previous to walk through it one hop at a time. The dashed box is the sender and the filled box is the receiver. Each step lists the checks that run there; a linked code is the error you see when that check fails.

Your application’s code is the same for every flow: it redirects to /sso/authorize, checks state on its callback and exchanges the code server to server. OhAuthCat handles the protocol differences.

  1. Step 1 of 8: Browser → Your app

    User asks to sign in

    The user enters a work email or picks their company. Your server creates state and a PKCE verifier and stores them with the browser session.

  2. Step 2 of 8: Your app → OhAuthCat

    Redirect to /sso/authorize

    The browser goes to the OhAuthCat auth host with your client ID, redirect URI, state, S256 challenge and a routing hint.

    Checks at OhAuthCat

  3. Step 3 of 8: OhAuthCat → IdP

    AuthnRequest to the IdP

    OhAuthCat sends a SAML AuthnRequest through the browser and remembers its request ID so the response can be matched to it.

  4. Step 4 of 8: inside IdP

    The IdP signs the user in

    The IdP authenticates the user with its own password, MFA and assignment rules. Errors here come from the IdP, not from OhAuthCat.

    Checks at IdP

    • User is assigned to the app (in the IdP)
  5. Step 5 of 8: IdP → OhAuthCat

    SAMLResponse posted to the ACS

    The browser posts the signed response to the connection's ACS URL. Every check below must pass; one failure refuses the sign-in.

    Checks at OhAuthCat

  6. Step 6 of 8: inside OhAuthCat

    Admission and roles

    OhAuthCat applies the organization's domain, policy and role rules to the validated identity.

    Checks at OhAuthCat

  7. Step 7 of 8: OhAuthCat → Your app

    Code back to your callback

    The browser is redirected to your exact redirect URI with a single-use code and your state. Your callback checks the state against the stored attempt and consumes it once.

    Checks at Your app

    • State matches the stored attempt
  8. Step 8 of 8: Your app → OhAuthCat

    Server-to-server code exchange

    Your server posts the code, the PKCE verifier and the redirect URI to /v1/sso/token on the auth host. The browser is not involved. You receive an access token and the profile.

    Checks at OhAuthCat

Without JavaScript, every step is listed in order. Use the left and right arrow keys to move between the flow tabs.

See how SSO works for the application side, IdP-initiated sign-in for the confirmation and handoff details, and IdP error fixes for errors the IdP shows before OhAuthCat is reached.