Skip to content

Blog

SAML vs OIDC: two ways to do SSO

SAML vs OIDC: both give you single sign-on. How SAML and OpenID Connect differ, which is easier to set up, which your tools use, and what it costs.

· 8 min read

SAML vs OIDC is a choice between two ways of doing the same job: single sign-on. SAML is an XML standard from 2005, built for workplace web apps; OIDC (OpenID Connect) is a JSON standard from 2014, built on OAuth 2.0 for web and mobile apps alike. Both let a person log in once to an identity provider and be accepted by other apps.

For a small business the choice is rarely yours. Each tool supports one, the other, or both, and your identity provider handles all of it. What does matter is which plan the tool puts it on.

The short answer

Use SAML when a workplace tool's SSO settings ask for an entity ID, an ACS URL and a certificate. That is most business SaaS. Use OIDC when a tool asks for a client ID, a client secret and an issuer URL, or when "Sign in with Google" or "Sign in with Microsoft" is enough for you.

Either way, your people will not notice which one is in use. Both end with them signed in, and both leave the same things undone afterwards.

SAML: XML, browser redirects, built for workplace SaaS

In a SAML login, the identity provider writes an XML document, the assertion, saying who the person is, signs it, and sends it to the tool through the person's browser. The tool checks the signature against a certificate it was given during setup.

SAML 2.0 was approved as an OASIS Standard in March 2005, for exactly the job companies still use it for: employees logging in to web-based business software through their company's directory. It does that well. It was not designed for mobile apps or APIs, and handling signed XML in code is fiddly, which is part of why tools treat it as a premium feature. What SAML is covers it in more detail, down to what sits inside an assertion.

OIDC: JSON tokens, built on OAuth, built for apps

OpenID Connect adds a login layer to OAuth 2.0, the standard apps use to get permission to each other's data (SAML vs OAuth explains that part). The OpenID Foundation published OpenID Connect Core 1.0 in February 2014.

In an OIDC login, the app sends the person to the identity provider, gets back a short code, and swaps that code, server to server, for an ID token: a signed JSON Web Token (JWT) listing who the person is. Because it uses JSON and plain HTTPS calls, OIDC is easier for developers to build and works the same in a browser, a phone app or a desktop app. "Sign in with Google", "Sign in with Microsoft" and "Sign in with Apple" are all OIDC. What OIDC is shows a decoded ID token and every field in it.

How the two logins differ

Trace one login through each and the difference is mostly about where the proof travels.

In SAML, the proof itself rides through the browser. The identity provider hands the browser a signed assertion, the browser posts it to the tool, and the tool checks it. The tool and the identity provider never talk directly during the login. That is simple to deploy, and it is why SAML needs a strong signature on every assertion: the browser is carrying the valuable thing.

In OIDC's usual flow, the browser carries only a short-lived code. The tool's server then calls the identity provider's token endpoint directly and gets the ID token back over that private channel. The valuable thing never sits in the browser's address bar. Phone and single-page apps, which cannot keep a client secret, add a one-off proof called PKCE so that a stolen code is useless to anyone else.

Neither approach is unsafe when done properly. They are two answers to the same question, written ten years apart for different kinds of software.

Side by side

SAML 2.0OpenID Connect
Published20052014
Built onIts own XML standardOAuth 2.0
TokenSigned XML assertionSigned JSON Web Token (ID token)
How it travelsPosted through the browserCode through the browser, token fetched by the server
Setup fieldsEntity ID, ACS URL, certificateClient ID, client secret, issuer or discovery URL
Good forWorkplace web appsWeb, mobile and desktop apps, and APIs
Common inEnterprise SaaS SSO settingsSocial login, newer SaaS, developer tools

Which is easier to set up?

With an identity provider's ready-made preset for a popular tool, both take minutes. Done by hand, OIDC is usually simpler.

A SAML setup means swapping metadata in both directions: the identity provider's sign-in URL, entity ID and certificate go to the tool, and the tool's ACS URL and entity ID go to the identity provider. Then there is ongoing upkeep. Signing certificates expire, and Google's SAML certificate page, as we read it on 27 October 2026, gives its certificates a five-year lifetime, after which SSO to the apps using them stops until someone rotates them.

An OIDC setup usually needs three values: the issuer, a client ID and a client secret. The tool reads everything else from the identity provider's published discovery document, including the current signing keys. When the provider rotates its keys, the tool picks up the new ones without anyone touching it. That quiet maintenance advantage is the best practical argument for OIDC when a tool offers both. The client secret is the thing to guard and to rotate if anyone who saw it leaves.

Which your tools support

Most established business tools offer SAML for SSO, because that is what enterprise buyers asked for first. A growing number also accept OIDC, and many offer "Sign in with Google" or "Sign in with Microsoft" to everyone, on every plan.

That last point is worth a minute. Signing in with Google is OIDC single sign-on in practice: one Google account, no separate password, Google's MFA rules. What it usually is not is enforced. The tool still allows email-and-password accounts, and you cannot require that everyone at your domain logs in through Google unless you are on the plan with "real" SSO. That enforcement, plus the admin controls around it, is what tools charge for.

Can you use OIDC instead of SAML for a specific tool, such as Slack? Only if that tool offers it for enforced SSO. Each vendor decides which protocols its SSO settings accept, and many business tools only offer SAML there. The tool's SSO documentation will say.

Is Google Workspace SAML or OIDC?

Both. Google Workspace can act as a SAML identity provider for third-party apps you add in the admin console, and it is an OIDC provider every time someone clicks "Sign in with Google". Microsoft Entra ID and Okta also support both. Google Workspace SSO covers using Google as your identity provider in detail.

Is OIDC replacing SAML?

Slowly, for new software. Developers prefer it, it works on phones, and the setup is lighter. But SAML is still the most common SSO option in business software, and identity providers will support both for a long time. Nobody is going to switch off SAML in the tools you already use. Types of SSO puts both among the other things that get called single sign-on.

When a tool offers both, which to pick

Some tools let you choose. A few plain rules settle it.

Pick the one your identity provider has a preset for. A preset fills in the URLs, the attribute names and often the provisioning settings, and it has been tested by thousands of other admins. A hand-built connection in the "better" protocol is worse than a preset in the other one.

If there is no preset, lean to OIDC. Fewer fields, no XML, and key rotation that looks after itself. Store the client secret where your other admin credentials live, not in a chat message.

Stick with SAML if you need something only your SAML setup does. Some tools read group membership or a role from SAML attributes and not from OIDC claims, or only support just-in-time account creation through one of them. Check the tool's documentation for what each option passes through before you switch.

Do not migrate a working connection for its own sake. If a tool has run on SAML for three years, the only urgent job is to know when its certificate expires.

Take a 20-person company on Google Workspace with one tool that supports both and has no Google preset for OIDC but does for SAML. Use the SAML preset. Put the certificate's expiry date in the shared calendar, keep one admin account outside SSO, and move on to the next tool.

Does it matter for cost?

Not directly. Tools rarely price SAML and OIDC differently; they price "SSO", and put it on Business or Enterprise plans whichever protocol it uses. What costs money is the plan that lets you enforce login through your identity provider. For a 20-person team, moving five common tools to the plans that include SSO comes to about $18,700 a year. The SSO tax post has the table, and the calculator does your own tools.

The cheap move, whatever the protocol: turn on "Sign in with Google" or "Sign in with Microsoft" wherever a tool offers it on the plan you have, and enforce MFA in your identity provider. You get most of the day-to-day benefit for nothing. If you then need enforced SSO for a contract, how to implement SSO in a small company puts the work in order, and what SSO is covers when it is worth paying for.

Where SmashSSO fits

Neither protocol creates, changes or removes accounts in your tools. They only handle the moment of login. Someone you disable in Google still has a Slack account, a GitHub seat and a Figma license until somebody removes them.

That is the part SmashSSO does. It reads your people from Google Workspace with read-only access, shows who has access to each tool and with what role, and invites, changes and removes people from one place, through a tool's member API where you have added a token and through an agent in your own Chrome otherwise. That browser has to be open for agent runs, and they can fail when a tool changes its screens. It is not SSO and does not touch how people sign in. It costs a flat fee from $199 a month billed annually (pricing).

FAQ

Is OIDC replacing SAML?
Slowly, for new apps, because it is simpler to build and works well on mobile. SAML is still the most common SSO option in business software, and identity providers will support both for a long time.
Can I use OIDC instead of SAML for Slack?
Only if the tool offers it. Each tool decides which protocols it accepts for enforced SSO, and many business tools only offer SAML there, so check the tool's SSO documentation.
Which is easier to set up, SAML or OIDC?
With an identity provider's ready-made preset, both take minutes. Done by hand, OIDC is usually simpler: a client ID, a secret and an issuer URL, with signing keys picked up automatically, instead of XML metadata and certificates that expire.
Is Google Workspace SAML or OIDC?
Both. Google Workspace can be a SAML identity provider for third-party apps added in its Admin console, and it is an OpenID Connect provider whenever someone uses "Sign in with Google".

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