Skip to content

Blog

How does SSO work? One login, step by step

How does SSO work? Follow one login from click to session: the redirect, the identity provider, the signed message, and why sessions outlive SSO.

· 9 min read

How does SSO work? It sends you away from the tool you want to use, to one login page your company controls, and back again with a signed note that says who you are. The tool checks the note's signature, trusts it, and opens a session for you. It never sees your password.

That round trip takes a second or two, and after the first login of the day it usually happens without you typing anything. Below is the same login traced one step at a time, with what each party knows at each moment, and the places where it goes wrong.

The short version

Three parties take part in every single sign-on login. You are one, in a browser. The tool, such as Slack or Figma, is the second; in SSO jargon it is the service provider, because it provides the service you came for. The third is the identity provider, such as Google Workspace, Microsoft Entra ID or Okta. It holds your company's list of people and is the only place your password is checked.

The tool and the identity provider agreed, once, during setup, to trust each other. The tool holds the identity provider's public key, a value that lets it check signatures but not make them. From then on the login goes tool, then identity provider, then tool again, with your browser carrying the messages both ways.

If you want the definitions first, what SSO is covers them. This post is the mechanics.

Step by step: the employee clicks Log in

Take Sam, at a company on Google Workspace, opening Figma on a Monday morning.

Sam goes to figma.com and types [email protected], or clicks "Log in with SSO". Figma looks up the domain. example.com has SSO configured, so Figma does not show a password box. It already knows which identity provider to use and where its login page is.

Then Figma builds an authentication request. It says, roughly: "Please confirm who this is, and send them back to this address." It adds a random value so it can recognize the reply later. Finally, Figma redirects Sam's browser to Google with that request attached to the address or posted in a hidden form.

Nothing has been checked yet. Figma has only decided where to send Sam. This is called SP-initiated login, because it started at the service provider. The alternative, IdP-initiated, starts when Sam clicks the Figma tile on his company's app launcher; the identity provider then sends a signed note without being asked. IdP-initiated login is convenient, but there was no request, so there is no random value for Figma to match the reply against. The tool has one check fewer.

The identity provider checks who they are (and MFA)

Now Sam's browser is on Google's login page, and Google decides how much to ask.

If Sam already has a Google session from checking his email earlier, Google skips the password. This is the "single" in single sign-on: one session at the identity provider, reused for every tool. If not, Google asks for his password, then his second factor: a code, a push prompt on his phone or a passkey. Multi-factor authentication (MFA) means proving who you are with two different kinds of evidence, usually something you know and something you have. SSO vs MFA covers how the two fit together.

Next, Google applies the company's rules. An admin may have set rules about MFA, the device or the location. If Sam's account is suspended, the login stops here. Last, Google checks that Sam is allowed to use Figma. Identity providers let admins assign each app to certain people or groups. In Google Workspace, a SAML app can be turned on for everyone, for organizational units or for groups. If Figma is not turned on for Sam, he gets an error instead of a login.

This step is where all the security of SSO lives. The tool has handed its whole login decision to the identity provider, so the identity provider's settings are now Figma's settings. That is what people mean by "SSO authentication": the tool authenticates no one itself; it trusts someone who did.

The assertion or token comes back

Once Sam passes, Google writes the note Figma asked for. What it looks like depends on the protocol the two agreed on.

With SAML, the older standard most workplace tools use, the note is an XML document called an assertion. It names Sam (usually by email), says when he signed in, which tool it is meant for and how long it is valid, usually a few minutes. Google signs it with its private key and the browser posts it to Figma. What SAML is goes through the fields.

With OpenID Connect (OIDC), the newer standard behind "Sign in with Google", the browser brings back a short one-time code instead. The tool's server swaps that code directly with the identity provider for an ID token, a signed piece of JSON with the same kind of facts. What OIDC is explains the token, and SAML vs OIDC compares the two routes.

Either way, Figma now runs its checks. Is the signature valid? It checks against the public key it stored at setup, so a forged or altered note fails. Is it meant for me? The note names its intended audience, and a note written for Slack is useless at Figma. Is it fresh? Old notes are rejected, which is why server clocks matter. Is it the reply to my request? The random value from earlier has to come back.

The last question is who is this? Figma matches the email or user ID to an account. If there is none, it either refuses or creates one on the spot, which is called just-in-time provisioning.

Sam's password never reached Figma. Figma got a signed statement about Sam, and that is all.

The tool creates a session, and why sessions outlive SSO

Figma now sets its own session cookie in Sam's browser, and from here on Figma does not ask Google anything. Every click Sam makes for the rest of the day is checked against Figma's session, not against the identity provider.

That detail explains most of the surprises people have with SSO. There are two sessions, not one. Google's session lets Sam into new tools without typing. Each tool's own session keeps him in that tool. They expire separately. Each tool also picks its own session length. Some keep you in for hours, others for weeks, and desktop and mobile apps often hold on longer than browsers. Some tools let an admin shorten it; many only on their top plans. And the identity provider is not asked again until the tool's session runs out, or the tool chooses to re-check.

So when people say "SSO keeps me logged in", what keeps them logged in is usually the tool's session. SSO only decides what happens at the moment a new session starts. Staying logged in and single sign-on are different things that happen to feel the same.

Do you still need passwords?

You need one: the password for your identity provider account, ideally backed by MFA or replaced by a passkey. Tools connected through SSO stop asking for their own.

The catch is the word "connected". A tool that is not on an SSO plan, or that you never set up, keeps its own password. And a tool that offers SSO but does not enforce it may still have an old password account from before you switched. Until you turn on "require SSO" in that tool, Sam could log in either way. That is why the setup checklist for any tool ends with enforcement, tested on one account before everyone.

What happens when someone leaves

Say Sam leaves on Friday and his admin suspends him in Google Workspace. Here is what that does, and does not do.

New logins stop. Next time any SSO-connected tool sends Sam to Google, Google refuses. That is real, and it is the main reason companies buy SSO.

Open sessions keep working. If Sam's laptop or phone still has a Figma session, Figma does not know Google said no, because Figma is not asking. Logout signals between identity provider and tool do exist: SAML has a Single Logout profile, and OpenID Connect has separate front-channel and back-channel logout specifications. Support for them varies by tool, so unless the tool supports one and you have set it up, the session lasts until it expires or someone ends it in the tool's admin page.

The account stays. Sam's Figma account still exists, still owns his files and very likely still takes a paid seat. SSO does not create or delete accounts. That is provisioning, usually through SCIM; SCIM vs SAML explains the split.

Tools outside SSO are untouched. Anything Sam logged in to with a password, or with "Sign in with Google" on a tool where you never set up enforced SSO, keeps working if he still has the password or a session.

The full list of what to do on the day is in our employee offboarding checklist.

Where it breaks

The login has several moving parts, and each one fails in a recognizable way.

Expired certificate. SAML signing certificates have an end date. Google's own help page on SAML certificates, as we read it on 27 October 2026, gives them a five-year lifetime and says that if one expires before you rotate it, users cannot use SSO for the apps that rely on it. Put the dates in a calendar.

Clock drift. The note is valid for minutes, so a server with the wrong time rejects good notes as expired. Email mismatch is the next most common. The identity provider sends [email protected], the tool has [email protected], and the tool refuses Sam or creates a duplicate account. App not assigned looks like a broken tool: Sam is in the identity provider but not given the app, so he gets an access error.

The identity provider is down. Every SSO-connected tool is locked for new logins at once. Keep a break-glass admin account that can log in without SSO wherever the tool allows it. Lockout after enforcement is the self-inflicted version. Turn on "require SSO" before testing it, and you can lock yourself out. Test with one account first.

None of these is exotic. They are the reason SSO needs an owner, even in a small company. How to implement SSO in a small company puts the setup in a safe order.

Where SmashSSO fits

SmashSSO is not part of this flow. It is not an identity provider, it does not issue assertions or tokens, and people keep logging in to each tool the way they do now.

It covers the step SSO skips: the accounts themselves. It reads your people from Google Workspace with read-only access and shows who has an account in each tool, and with what role. When someone is suspended in Google Workspace, it alerts you and lists every tool where they still have access, then removes them, through the tool's member API where you have added a token, or through an agent in your own Chrome, where you are already signed in as an admin. That agent needs your browser open, is slower than an API, and can fail when a tool redesigns its screens; a failed run says so. Every change goes in an audit log.

It costs a flat fee from $199 a month, billed annually (pricing). If a contract or an auditor needs enforced login through an identity provider, you need real SSO for those tools; SmashSSO handles the accounts around it. How it works shows the flow.

FAQ

How does SSO authentication work?
The tool sends your browser to your company's identity provider, such as Google Workspace or Okta. You sign in there, with MFA if required, and the identity provider sends back a signed message saying who you are. The tool checks the signature and opens a session, without ever seeing your password.
Do I still need passwords with SSO?
You need one: the password for your identity provider account, ideally with MFA or a passkey. Tools connected through SSO stop asking for their own. Tools that are not connected, or that do not enforce SSO, keep their own passwords.
What happens to open sessions when I disable someone in my identity provider?
Usually nothing straight away. After login each tool runs its own session and does not check back with the identity provider, so an open session on a laptop or phone can keep working until it expires or an admin ends it in the tool. Disabling the person stops new logins only.
Is SSO the same as staying logged in?
No. Staying logged in is the tool's own session, which lasts as long as the tool decides. SSO only handles the moment a new session starts, by letting your identity provider vouch for you instead of the tool checking a password.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google