Skip to content

Blog

What is SAML? A guide for people who will never read the spec

What is SAML? The standard behind most workplace SSO: how a SAML login works, what an assertion holds, how setup goes, and why it costs extra.

· 10 min read

What is SAML? SAML, short for Security Assertion Markup Language, is the standard most workplace tools use for single sign-on. It lets one trusted service, your identity provider, tell a tool "this person is Ana, she has just signed in", in a signed message the tool can check. The tool believes the message and lets Ana in without a password of its own.

When a tool's pricing page says "SAML SSO", this is what it means. The current version, SAML 2.0, was approved as an OASIS Standard in March 2005, and it is still how most business software does SSO.

SAML in one paragraph

SAML is a format for messages about people, written in XML and signed with a certificate. The identity provider writes the message (an "assertion") saying who the person is and that they have authenticated. The tool reads it, checks the signature against the certificate it was given during setup, and opens a session. Nothing else crosses between the two: the tool never sees the password.

That is also what "SAML SSO" means on a feature list. SSO is the goal, one login for many tools; SAML is the most common way to get there. What SSO is covers the goal in general, and SAML vs SSO untangles the two words for anyone who has heard them used as synonyms.

The two sides: identity provider and service provider

Every SAML connection has two parties.

The identity provider (IdP) holds your people and checks their passwords and MFA. Google Workspace, Microsoft Entra ID, Okta, JumpCloud and OneLogin all act as SAML identity providers. If your company runs on Google Workspace, you already have one; what an identity provider is explains whether you need another.

The service provider (SP) is the tool being logged in to: Slack, GitHub, Figma, Jira. It trusts the identity provider and accepts its assertions.

You set the connection up once per tool. After that, the identity provider is the only place a password is typed.

A SAML login, step by step

Here is what happens when Ana opens Figma at a company that uses SAML through Google Workspace. Most of it happens in under a second, in browser redirects she never notices.

Ana goes to Figma and enters her work email, or clicks "Log in with SSO". Figma recognizes the domain and builds a short request: "please authenticate this person and send them back to me". Her browser carries that request to Google. SAML uses the browser as the messenger; in the usual web login, the tool and the identity provider never talk directly.

Then Google checks who she is. If she is already signed in to Google, it skips this. If not, she enters her password and second factor. Google writes a signed assertion with Ana's email, the time, how long it is valid for, and which tool it is meant for. Her browser posts the assertion to Figma, and Figma checks the signature against Google's certificate, checks the time and the audience, matches the email to a Figma account, and signs her in.

The flow can also start at the identity provider: Ana clicks the Figma tile in her Google apps menu, and Google sends an assertion without being asked. That is called IdP-initiated login; the first version is SP-initiated. How SSO works follows the same round trip with what each side knows at each moment.

What is inside a SAML assertion

The assertion is the whole point of SAML, so it is worth knowing what it carries. The SAML 2.0 technical overview from the OASIS committee that wrote the standard describes three kinds of statement an assertion can hold. An authentication statement says the person signed in, when, and how. An attribute statement carries facts about them, such as email, name or group. An authorization decision statement says whether they may do something; workplace SSO rarely uses this one.

Around those statements sit a few elements that every tool checks. The Issuer names the identity provider that wrote it. The Subject names the person, through a value called the NameID, which in most workplace setups is the email address. The Conditions set a validity window, with a NotBefore and a NotOnOrAfter time, and an AudienceRestriction naming the one tool the assertion is for. Then comes the signature, which covers all of it.

Each element closes off a specific attack. The signature stops someone forging or editing an assertion. The audience stops an assertion written for one tool being replayed at another. The short validity window stops an old assertion being reused next week. A tool that skips any of these checks has a hole, which is why "SAML is secure" always comes with "when it is implemented properly".

The same overview describes the bindings, the ways a SAML message can travel. The two you will meet are HTTP Redirect, where a request rides in the address bar, and HTTP POST, where the assertion is posted through a hidden form. That is why setup screens sometimes ask you to pick between "Redirect" and "POST".

Metadata, certificates and the setup screen

Setting up SAML for a tool means swapping a few values between the two admin consoles. Each side publishes "metadata", which is an XML file or a set of fields.

From the identity provider to the tool go the sign-in URL, the entity ID (a unique name for the identity provider), and the signing certificate. From the tool to the identity provider go the Assertion Consumer Service (ACS) URL, where assertions are posted, and the tool's own entity ID. Then you agree the attribute mapping: which field holds the email, and sometimes the first name, last name or group.

Here is what that looks like in Google Workspace, from Google's custom SAML app help page as we read it on 27 October 2026. A super administrator goes to Menu, then Apps, then Web and mobile apps, and chooses Add app, then Add custom SAML app. Google shows its SSO URL, entity ID and certificate, or a metadata file to download, and you paste those into the tool. Then you enter the tool's ACS URL, which must start with https://, and its entity ID. The Name ID defaults to the person's primary email, which is what most tools expect. Last, you turn the app on for everyone, for certain organizational units, or for certain groups. Google says changes can take up to 24 hours, though they are usually faster. Google Workspace SSO goes further into using Google as your identity provider.

Most tools give you a form for their side, and most identity providers have a preset for popular tools that fills in half of it. For a common tool it is a short job. For an unusual one it can be an afternoon of matching field names.

What breaks: certificate expiry, clock drift, wrong email

SAML is old and stable, but a few failures come up again and again.

The certificate expires. Signing certificates have an end date. Google's SAML certificate page gives its certificates a five-year lifetime and says that if one expires before you rotate it, people cannot use SSO for the apps that rely on it. The fix is to add a new certificate, update each tool, and only then remove the old one. Put the dates in a calendar, because five years is long enough for everyone who set it up to have left.

Clocks drift. Assertions are valid for a few minutes. If a server's clock is off, valid logins are rejected as expired.

The email does not match. If the identity provider sends [email protected] and the tool account is [email protected], the tool either rejects her or creates a second account. Name changes and domain changes cause this months after setup.

Someone is locked out. If SAML is enforced and the connection breaks, nobody can log in. Keep one admin account that can bypass SSO, where the tool allows it, and test enforcement with one account before switching everyone over.

Is SAML secure?

Yes, when both sides do their checks. The tool never sees a password, assertions are signed and short-lived, and the identity provider can enforce MFA for every connected tool at once. The weak points are in implementations, not the standard: tools that check signatures loosely, certificates nobody rotates, and email addresses that drift out of step. The other weak point is the identity provider account itself. With SAML in front of everything, a phished identity provider login opens every connected tool, so that account needs your strongest MFA.

Is SAML outdated?

It is old, not obsolete. Newer apps often prefer OpenID Connect, which uses JSON instead of XML and works more naturally in phone apps. What OIDC is explains it, and SAML vs OIDC compares the two. But SAML is still the SSO option most business tools offer, and the identity providers listed above support both. For a small company the question rarely comes up: you use whatever the tool supports.

Why tools charge for it

A SAML login works the same way for a team of 10 as for a company of 10,000. What it does for a vendor is separate customers: large companies cannot buy software without it, so putting SAML on the top plan makes every large company buy the top plan. Small companies that want it for tidier offboarding pay the same price, per seat.

That is the SSO tax. Slack puts SAML on Business+, GitHub on Enterprise, Figma on Organization. The SSO tax calculator adds up what that means for your tools. So the answer to "does SAML need an Enterprise plan?" is no technically, and very often yes commercially.

What SAML does not do

SAML handles the moment of login and nothing else. It does not create accounts in advance, it does not change someone's role, and it does not remove anyone from a tool when they leave. Some tools create an account the first time someone logs in through SAML, which is just-in-time provisioning, but none delete one through SAML. Removing accounts is the job of a different standard, SCIM, covered in what SCIM is.

Should a small company set up SAML?

Start with the tools that already include it on the plan you pay for. Connecting those costs nothing but an hour, and it puts their logins behind your Google Workspace MFA. Do one tool first, with a break-glass admin account kept outside SSO, and enforce it only after a test login works.

Then look at the tools that would need an upgrade, and ask why you want SAML there. If a customer contract or an auditor names it, the upgrade is a cost of that contract. If the honest reason is "so leavers lose access", SAML is the wrong purchase: it blocks their next login and leaves the account, the seat and any open session in place. A 5-person team with one leaver a year rarely gets its money back. A 50-person team with monthly leavers gets more from SAML, but still needs something that removes accounts.

SAML and SmashSSO: different jobs

SmashSSO does not use SAML and does not sit in your login path. People keep logging in to each tool exactly as they do today.

What it does is the part SAML leaves out: it reads your people from Google Workspace with read-only access, shows who already has an account in each tool and with what role, and invites, changes and removes them from one place, through each tool's member API where you have added a token and through an agent in your own Chrome where you have not. That browser has to be open for agent runs, which are slower than an API and can fail when a tool redesigns its screens. It needs no upgrade in any tool, and costs a flat fee from $199 a month billed annually (pricing).

If a customer contract or an auditor requires SAML login for certain systems, set it up for those systems. SmashSSO is for the access work around them.

FAQ

What does SAML stand for?
Security Assertion Markup Language. It is an XML-based standard, approved by OASIS as SAML 2.0 in March 2005, that lets an identity provider tell a tool, in a signed message, who a person is and that they have just signed in.
Is SAML secure?
Yes, when it is set up properly. The tool never sees the person's password, and every assertion is signed, short-lived and addressed to one tool. Most real-world problems come from tools that check signatures loosely, expired certificates, mismatched email addresses, or a weakly protected identity provider account.
Is SAML outdated?
It is old, not obsolete. Newer apps often prefer OpenID Connect, but SAML is still the most widely offered way to do single sign-on into business software, and most identity providers support both.
Does SAML need an Enterprise plan?
Not technically, but commercially it often does. Many tools keep SAML SSO for their Business or Enterprise plans: Slack on Business+, GitHub on Enterprise, Figma on Organization. That upgrade is known as the SSO tax.

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