Skip to content

Blog

SAML vs SSO: what's the difference?

SAML vs SSO: SSO is the goal, SAML is one protocol that delivers it. How they relate, where OIDC and SCIM fit, and what SAML SSO means for your bill.

· 8 min read

SAML vs SSO is not a choice between two options. SSO (single sign-on) is the goal: one login that gets your people into all their tools. SAML is one of the protocols used to build it: the agreed format in which an identity provider tells a tool "this person is who they say they are". Asking "SAML or SSO?" is a bit like asking "HTTPS or websites?"

Most of the time, when a pricing page says "SAML SSO", it means single sign-on built with SAML, and it is the line that pushes you onto a more expensive plan. Here is how the pieces fit, what the difference between SSO and SAML means in practice, and what each one means for your bill.

SSO: the experience

Single sign-on is what your employees see. They sign in once, to Google Workspace, Microsoft or a dedicated identity provider such as Okta, and from then on they can open Slack, GitHub or Figma without typing another password. What SSO is, in plain English covers the idea from scratch.

For whoever runs the tools, SSO means three things. Login rules such as MFA and password strength are set once, in the identity provider, instead of in every tool. Disabling someone in the identity provider stops them signing in to every connected tool from then on. And people have fewer passwords to reuse and lose.

SSO describes the outcome. It says nothing about how the identity provider and the tool talk to each other. That is where protocols come in.

SAML: one way to deliver it

SAML (Security Assertion Markup Language) is an open standard for passing login information between an identity provider (IdP: the system that knows your people) and a service provider (SP: the tool they want to use). The version in use today, SAML 2.0, dates from March 2005, per the references in the OASIS technical overview of the standard.

A typical SAML login goes like this. Your employee opens the tool and clicks "Log in with SSO". The tool redirects their browser to your identity provider with a request: please authenticate this person. The identity provider signs them in, or recognizes that they already are, and checks MFA. It then sends the browser back to the tool carrying a SAML assertion: an XML document stating who the person is, signed with the identity provider's certificate. Finally, the tool checks the signature against the certificate it was given during setup, trusts the assertion and creates a session.

The setup is a one-time exchange: the tool gets the identity provider's sign-in address and certificate, and the identity provider gets the tool's address and identifier. After that, logins just work, until the certificate expires, which is the classic way SAML SSO breaks on a random Tuesday. What SAML is, for people who will never read the spec goes deeper on assertions and certificates.

Two ways a SAML login can start

The OASIS overview describes two starting points, and you will meet both in admin settings.

SP-initiated is the flow above. The person goes to the tool first, through a bookmark or a link, and the tool sends them to the identity provider to log in.

IdP-initiated starts at the other end. The person is already signed in to the identity provider, opens its dashboard of apps, and clicks the tool's tile. The identity provider sends them to the tool with an assertion they never asked the tool for.

Both are SAML, and both are SSO. The difference shows up when you set up a tool and its settings ask which flows to allow, and when people start from the identity provider's dashboard of app tiles, which is the IdP-initiated flow.

What is SAML SSO?

"SAML SSO" just means single sign-on where the login is passed with SAML. It is the most common way workplace software does SSO, which is why the two words have fused on pricing pages and in search results. When a vendor lists "SSO" with no protocol named, it nearly always means SAML.

That fusion is where most of the confusion comes from. People read "SAML SSO" as one feature, and assume it covers everything an identity provider can do. It covers one thing: the login. The other things, such as creating accounts, changing roles and removing people, are separate features with separate names, covered below.

The other protocols: OIDC, and "Sign in with Google"

SAML is not the only way to build SSO.

OpenID Connect (OIDC) does the same job with JSON tokens instead of XML. It is built on top of OAuth 2.0, it is newer, and it is common in mobile and consumer apps. Some workplace tools support it alongside or instead of SAML. SAML against OIDC compares the two directly, and SAML against OAuth explains why OAuth on its own is about permissions, not login.

"Sign in with Google" or "Sign in with Microsoft" buttons usually use OIDC under the hood. They save your people a password, but whether they count as company SSO depends on the tool. If the tool lets anyone with any Google account sign in, and does not let you require it for your domain, you control less than you think: their account in the tool still exists independently, often with its own password as a fallback.

Which protocol a tool uses is almost always decided by the tool. You do not choose SAML over OIDC; you use whatever the tool supports on the plan you pay for.

SCIM: the part people assume SAML does

Here is the misunderstanding that costs small companies the most. SAML only handles signing in. It does not create accounts, change roles or remove anyone.

When someone leaves and you disable them in your identity provider, SAML stops them logging in again. But their account in each tool is still there: still a member, often still holding a paid seat, sometimes with an open session that keeps working until it expires, and with any API tokens they created still valid.

Creating and removing accounts is called provisioning, and the standard protocol for it is SCIM (System for Cross-domain Identity Management). With SCIM, your identity provider calls the tool's API to add, update and deactivate people automatically. Tools that support SCIM often keep it on the same expensive plan as SAML, or on an even more expensive one. SCIM against SAML lays the two side by side.

So the full picture has three layers. SSO is the goal, one login. SAML, or OIDC, is how the login is passed. SCIM is how accounts are created and removed. A tool can have the first two without the third, and many do.

Where SAML SSO goes wrong in a small company

Knowing the parts helps you spot the failures before they cost you.

Certificates expire. The identity provider signs every assertion with a certificate that has an end date. When it lapses, every login to that tool fails until someone uploads the new one on both sides. Put the dates in a calendar.

Emails do not match. Most workplace tools match a SAML login to an account by email address. If someone's account in the tool uses an old or personal address, the assertion arrives for a person the tool does not know, and the login fails or creates a duplicate account.

Local passwords survive. If a tool allows a password login alongside SAML, and you have not switched that off, anyone who uses it is outside SSO. Disabling them in the identity provider does nothing to that login.

Nobody owns it. In a 15-person company, the person who set up SAML on a tool is often the only one who knows how. When they leave, the setup becomes an orphan.

What "SAML SSO" on a pricing page means for your bill

When a plan comparison lists "SAML SSO", it means that plan lets you connect the tool to your identity provider. It is very often missing from the plans small companies buy: Slack lists it on Business+, GitHub on Enterprise, Figma on Organization. That gap is called the SSO tax, and for a 20-person team on five common tools it adds up to about $18,700 a year.

Two things are worth checking on any pricing page. First, which plan has SAML? That is the plan you would need for SSO. Second, which plan has SCIM or "user provisioning"? That is the plan you would need for automatic removal. If it is higher still, SSO alone will not solve offboarding. What "enterprise SSO" means shows how vendors bundle the two.

Which one you need

You do not pick between SAML and SSO. You decide whether you need SSO at all, and then use whatever protocol each tool supports.

If a customer, auditor or insurer requires login through an identity provider, you need SSO, which in practice means SAML for most workplace tools. Budget for the tool upgrades, and limit them to the systems the requirement names.

If what you want is to add and remove people across your tools from one place, SAML will not do that by itself, and SCIM usually costs even more.

Where SmashSSO fits

That second job is what SmashSSO does instead. It is not SSO and does not touch logins: it reads your people from Google Workspace, shows who has an account in each tool and with what role, and invites, changes and removes them through a tool's member API where you have added a token, and otherwise through an agent in your own Chrome, in tabs where you are signed in as an admin. The agent needs that browser open and can fail when a tool changes its screens. It costs a flat fee from $199 a month billed annually rather than an upgrade on every tool; see pricing.

For the bigger question of whether SSO is worth it for your company, read SSO for small business: do you actually need it?

FAQ

Is SAML the same as SSO?
No. SSO (single sign-on) is the experience: one login for many tools. SAML is a protocol, a set of rules for how an identity provider tells a tool who you are. SAML is one of the ways SSO is built; OpenID Connect is another.
Is SAML better than OIDC?
Neither is better in general. SAML is older, XML-based and the norm for workplace SaaS; OIDC is newer, JSON-based and common for consumer and mobile logins. You use whichever the tool supports.
Does SAML SSO add and remove users?
No. SAML only handles signing in. Creating and removing accounts in a tool is provisioning, done with SCIM or by hand, and it is often on a more expensive plan again.
What does 'SAML SSO' mean on a pricing page?
That the plan lets you connect the tool to an identity provider such as Okta, Google or Entra ID using SAML. It is the line most often reserved for Business or Enterprise plans.

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