Skip to content
Scope an integration

Glossary

What is SAML SSO?

SAML SSO lets users sign in to an application with their company identity provider, using the SAML 2.0 standard to pass a signed login assertion.

SAML single sign-on lets employees log in to a SaaS application through their company identity provider, such as Okta, Microsoft Entra ID or Google Workspace. Using the SAML 2.0 standard, the identity provider authenticates the user and sends the application a digitally signed assertion, so the application never handles the user’s password.

How does it work?

  1. The user opens the application (service provider) and is redirected to the company identity provider.
  2. The identity provider authenticates the user, often with MFA.
  3. It posts a signed XML assertion back to the application’s Assertion Consumer Service (ACS) URL.
  4. The application validates the signature, reads attributes such as email and groups, and starts a session.

SAML is older and XML-based; OpenID Connect is a newer, JSON-based alternative built on OAuth 2.0. Many enterprise customers still standardise on SAML, so SaaS products selling upmarket usually support it first.

Where it shows up in integrations

  • Enterprise readiness Most enterprise buyers require SSO before rollout, and many expect it alongside SCIM provisioning.
  • Learning platforms Learners reach the LMS from the company portal without a separate password.
  • Multi-tenant SaaS Each customer brings its own identity provider, certificate and attribute mapping, configured per tenant.

Common pitfalls

  • Not rotating or monitoring signing certificates, so logins fail when a certificate expires.
  • Trusting attributes without validating the signature, audience and timestamps of the assertion.
  • Creating duplicate accounts because the SSO identifier differs from the one used for provisioning.
  • Forgetting a fallback admin login for when the customer’s identity provider is misconfigured.