Skip to content
BENIBIX Learn

Security Assertion Markup Language (SAML)

Development🔑 AuthSingle Sign-On

Also known as SAML, SAML 2.0, SAML SSO, SAML Assertion

An XML standard for single sign-on. A signed note tells the app who you are.

Think of it like

Think of it like a signed note from the school office. The teacher reads it and lets you in.

Example

Emma opens Salesforce at work. It sends her to her company's Okta page, where she signs in. Okta posts a signed SAML assertion back, and Salesforce lets her in.

Why it matters

Most big work apps still take SAML. Setting up company sign-in for them often means trading SAML settings with the app.

Definition

SAML is an older standard for single sign-on, built on XML. When you open a work app, the app sends you to the identity provider. The provider checks who you are. Then it gives your browser a signed XML note, called an assertion, to post back to the app. The app checks the signature and lets you in. Version 2.0 became a standard in 2005.

Example code

xml
<saml:Assertion Version="2.0" IssueInstant="2026-11-18T09:00:00Z">
  <saml:Issuer>https://idp.example.com</saml:Issuer>
  <ds:Signature>...</ds:Signature>
  <saml:Subject>
    <saml:NameID>emma@example.com</saml:NameID>
  </saml:Subject>
</saml:Assertion>
The heart of an assertion. It names who signed it, then who the user is.
SAML is the top lane. It runs each time Emma signs in, and carries one signed note.

Common mistake

Trusting an assertion without checking its signature and who it is for. A copied or changed note must be turned away.

Key takeaways

  1. 1
    A signed note. The assertion is XML with a signature.
  2. 2
    Carried by the browser. Posted from the provider to the app.
  3. 3
    Made for work apps. Older than OpenID Connect, still everywhere.

Compare