Skip to content

SAML Explained in Plain English

Last checked November 15, 2026

SAML is a shared set of rules that lets an identity provider tell a service provider who someone is. The letters stand for Security Assertion Markup Language. It's an open standard for exchanging authentication and authorization data between parties, in particular an identity provider and a service provider.1

Authentication means proving who you are. Authorization means what you're allowed to do. SAML can carry both.

A language computers use

The "markup language" part means the messages are written in XML. Most SAML exchanges use a standardized dialect of it.1 XML is a way of labeling pieces of data, a bit like putting each fact on its own labeled card.

You won't read these messages as a business owner. Your admin panel hides them. But the names of their parts, like "assertion" and "attribute," turn up in settings screens, so it's worth knowing what they mean.

What's inside an assertion

An assertion is the statement the identity provider sends. Think of a note from the front desk to a teacher. It says this person checked in, plus a few facts about them.

The source says SAML provides three types of statements.1

  1. Authentication statement. It tells the app that the person did sign in with the identity provider at a particular time, using a particular method.1
  2. Attribute statement. It says the person is linked to certain attributes. An attribute is simply a name–value pair, such as a name and its value.1
  3. Authorization decision statement. It says the person is permitted to perform an action on a resource.1
What a SAML assertion can holdIdentity provider builds an assertionAuthentication statement: who, when, howAttribute statement: name-value factsAuthorization statement: allowed actionsSigned, then sent to the app
Up to three kinds of statement.

The authorization type is limited on purpose. The source says its expressiveness is intentionally limited.1 In everyday SSO, authentication and attribute statements do most of the work.

How the note is protected

An assertion that anyone could forge would be useless. SAML uses digital signatures, based on the XML Signature standard, for authentication and message integrity.1

"Integrity" means the note wasn't changed on the way. The signature lets the app check that.

Why older business apps still use it

Two reasons show up in the sources.

  • It solved a messy problem. SSO is relatively easy inside one security domain. Reaching across domains was harder and led to a proliferation of non-interoperable proprietary technologies. SAML's Web Browser SSO profile was specified and standardized to promote interoperability.1
  • It fits business software. In practice, SAML SSO is most commonly used for authentication into cloud-based business software.1

An app that already speaks SAML works with any identity provider that speaks it too. That's the point of an open standard.

Where newer methods come in

Wikipedia notes that as privacy rules tightened, newer methods like OpenID Connect have started to become more attractive.2 A separate lesson, OAuth and OpenID Connect, compares the two ideas.

SAML doesn't dictate how the identity provider checks you. That part is open. To see how a second check can slot in there, read SSO and multi-factor sign-in, which picks the thread up.

Cited material

  1. SAML, Wikipedia
  2. Single sign-on, Wikipedia