Skip to content

An SSO Login, Step by Step

Last checked November 15, 2026

You click "Sign in with SSO." Then you're in. A lot happens in between, and most of it is your browser carrying notes from one side to the other. It feels like one quick jump.

This page follows the common SAML version. The cast is familiar if you've read about the two sides of SSO. It's you, the app (the service provider), and the sign-in system (the identity provider), all passing notes through your browser.

Step 1: You ask the app for something

You go to the app. In SAML terms, the principal requests a service from the service provider.1

The app notices you haven't signed in yet. It has no password for you. It doesn't want one.

Version 2.0 of SAML starts here, at the app. Its browser flows begin with a request at the service provider.1

Step 2: The app asks the identity provider

The app wants to know who you are. So it issues an authentication request to the identity provider. It sends it through your browser, which the source calls the user agent.2

Your browser is the messenger. The app hands it a note. "Take this to the identity provider," it says. Off the browser goes.

How the note travels follows a set of rules called a binding. A SAML binding maps a SAML message onto standard messaging formats or communications protocols.1 You'll rarely need to think about this unless you're setting it up.

Step 3: The identity provider checks you

Now the identity provider takes over. It may request some information from you, such as a username and password.1

This is the place where you type something. That's the "single" in single sign-on. One identity provider can serve assertions to many service providers, so the same check can cover many apps.1

Step 4: A statement goes back to the app

You pass. Now the identity provider writes a short statement about you, called an assertion, and your browser carries it back to the app.

The SAML page shows what's inside.

One SSO loginYou open the appApp sends you to the identity providerIdentity provider checks youIdentity provider sends a statementApp reads it and lets you in
The usual order of events in a SAML sign-in.

Step 5: The app decides

The app reads the assertion. Then it makes its own decision about letting you in. That's an access control decision.1

The app keeps the final say. Satisfied? You land inside.

The same idea with OpenID Connect

Newer apps often use OpenID Connect instead of SAML. The order is much the same, but the words change. Details are on the OpenID Connect page.

With OpenID Connect, the app is called the client. It checks your identity based on the authentication done by an authorization server.3 What comes back is an ID Token. The spec calls it a security token that contains claims about your authentication.3

A claim is just one fact about you, like a name or an email address.

If a login fails

The exact error text depends on your identity provider and your app. Check their own help pages for what a given message means. Don't guess.

Cited material

  1. SAML, Wikipedia
  2. Single sign-on, Wikipedia
  3. OpenID Connect Core 1.0, OpenID Foundation