IT Glossary
SAML is an XML standard for exchanging authentication data and enabling SSO. Learn how SAML works, how it differs from SCIM, and where Corma fits in.
June 8, 2026
SAML (Security Assertion Markup Language) is an open, XML-based standard that lets an identity provider securely pass authentication and authorization data to a service provider. It is the protocol most commonly used to enable browser-based Single Sign-On for enterprise applications, allowing a user authenticated by the IdP to access a connected app without a separate login.
SAML and SCIM solve different problems and are often confused. SAML handles authentication at login time, while SCIM handles account provisioning before and after login.
A company rolls out SAML so employees reach Salesforce and Workday through one IdP login. But SAML alone does not create or delete the Salesforce account. If an employee leaves and only SAML is configured, the account can linger. Pairing SAML (login) with SCIM (lifecycle) closes that gap.
Yes. SAML remains the dominant SSO standard for enterprise web apps, even as OIDC grows for mobile and modern APIs.
SAML is built for authentication and SSO, while OAuth is built for authorization (granting access to resources). OIDC adds an authentication layer on top of OAuth.
No. SAML authenticates existing users. Creating and removing accounts is the job of SCIM or another provisioning method.
Corma layers governance on top of SAML SSO so login and lifecycle stay aligned. See automated provisioning or request a demo.