Auth0Alternatives
FeaturesOpen SourceSelf-hostedB2BB2C
SubmitSign In

Discover

LatestOpen SourceSelf-hostedB2BB2CAll providers

AI & Agents

MCP AuthorizationAgent IdentitiesToken VaultAI Agent DetectionDevice LoginAll features

Data Residency

πŸ‡ͺπŸ‡ΊEuropean UnionπŸ‡ΊπŸ‡ΈUnited StatesπŸ‡¬πŸ‡§United KingdomπŸ‡¨πŸ‡­SwitzerlandπŸ‡¦πŸ‡ΊAustraliaAll regions

Compliance

SOC2GDPRISO 27001HIPAAPCI DSSAll compliance
Submit
/Blog
/SAML vs OIDC vs OAuth: Which One Do You Need?

SAML vs OIDC vs OAuth: Which One Do You Need?

SAML and OIDC sign users in, OAuth gives apps access to APIs. How each works, how they differ, and which one your product needs.

Leonard Hußkeβ€’Nov 22, 2026β€’9 min read

SAML vs OIDC vs OAuth: SAML 2.0 uses an XML assertion for enterprise SSO, OpenID Connect uses an ID token (JWT) and is built on top of OAuth 2.0, which issues access tokens
On this page
  1. SAML and OIDC handle authentication, OAuth handles authorization
  2. SAML vs OIDC vs OAuth compared
  3. How SAML works
  4. How OpenID Connect works
  5. How OAuth 2.0 works
  6. SAML vs OIDC for enterprise SSO: support both
  7. Most auth providers support SAML, half support SCIM
  8. Pick the protocol by what you build
  9. FAQ

SAML and OpenID Connect (OIDC) sign users in. OAuth 2.0 lets an app call an API. If you are adding login to your own app, use OIDC. If you sell to companies, their IT teams often want employees to sign in through Okta, Entra ID, or Google Workspace. Many of those teams ask for SAML, so support it as well. If other apps, AI agents, or your own services call your API, use OAuth.

  • SAML 2.0 dates from 2005. It passes XML assertions through the browser and is the standard for enterprise single sign-on.
  • OpenID Connect dates from 2014. It adds an identity layer on top of OAuth 2.0 and returns an ID token, a JWT that says who signed in. It is the default for new apps.
  • OAuth 2.0 dates from 2012. It handles authorization, not authentication, and returns an access token that says what an app may do.
  • 33 of the 37 providers in our directory support SAML. 18 support SCIM, which B2B customers usually ask for at the same time.

SAML and OIDC handle authentication, OAuth handles authorization

People compare the three because all three appear on the same login screens. They answer different questions.

  • Authentication asks who the user is. SAML and OIDC answer that question.
  • Authorization asks what an app may do. OAuth answers that question.

The OAuth community's article on user authentication with OAuth 2.0 says that "OAuth 2.0 is not an authentication protocol". OAuth gives an app a token to call an API. The token says nothing reliable about who the user is. OpenID Connect adds what is missing, and its spec calls it "a simple identity layer on top of the OAuth 2.0 protocol".

The real comparison is SAML vs OIDC for signing users in. OIDC is built on OAuth, and OAuth controls access to APIs.

Which protocol do you need: to sign users of your own app in, use OpenID Connect. For employees of business customers signing in through their company IdP, use SAML 2.0 and OIDC. For third-party apps and AI agents calling an API on behalf of a user, use OAuth 2.0 with the code flow and PKCE. For machine-to-machine calls, use the OAuth 2.0 client credentials grant. SCIM keeps accounts in sync.

SAML vs OIDC vs OAuth compared

SAML 2.0OpenID ConnectOAuth 2.0
AnswersWho is this user?Who is this user?What may this app do?
PublishedMarch 2005, OASISFebruary 2014, OpenID FoundationOctober 2012, RFC 6749
TokenXML assertion, signed with XML SignatureID token in JWT format, plus an access tokenAccess token in a format the spec leaves open
Data formatXMLJSONJSON
TransportBrowser redirects and form postsBrowser redirects, then a back-channel callBrowser redirects, then a back-channel call
Works for mobile apps and single-page appsPoorlyYes, with PKCEYes, with PKCE
Works for APIs and machines
No
No, OAuth handles that
Yes
Typical useEmployees who sign in to SaaS through their company IdPLogin for your app, social login, and modern enterprise SSOThird-party API access, AI agents, and calls between services

How SAML works

SAML 2.0 is an OASIS standard approved in March 2005. Its core is the assertion, which the spec defines as "a package of information that supplies zero or more statements made by a SAML authority". In practice, the identity provider (IdP) tells your app who the user is and adds attributes such as email, name, and groups. SAML calls your app the service provider (SP).

The most common flow starts at your app. OASIS calls this flow "SP-initiated web SSO". SAML also supports IdP-initiated sign-in, where the user starts from a dashboard of apps.

SAML 2.0 service-provider-initiated sign-in in seven steps: the browser opens the app, the app redirects with an AuthnRequest, the browser follows it to the identity provider, the user signs in, the IdP returns an HTML form with a signed SAML Response, the browser posts it to the app's ACS URL, and the app checks the signature.

Three details matter when you build or buy SAML support:

  • The browser carries every message. The request usually travels in a redirect, which SAML calls the HTTP-Redirect binding. The response is a base64-encoded HTML form. The browser posts that form to your Assertion Consumer Service (ACS) URL, and SAML calls that step the HTTP-POST binding.
  • All of the security rests on the signature. With the POST binding, the assertion "MUST be signed". Before your app trusts anything in the assertion, it must check the signature, the issuer, the audience, and the time window.
  • XML signature checks are easy to get wrong. A 2012 USENIX Security study of 14 major SAML frameworks found that 11 had critical XML Signature wrapping flaws. Anyone who holds the IdP's signing key can also create assertions for any user, an attack called "Golden SAML". Use a maintained library or an auth provider instead of parsing SAML yourself.

The SAML standard is finished. The OASIS technical committee that wrote it closed in July 2023. Enterprises still use SAML widely, because many of their identity providers and admins already have it set up.

How OpenID Connect works

The OpenID Foundation finalized OpenID Connect Core 1.0 in February 2014. The current text includes errata set 2 from December 2023. In 2024, ISO/IEC published OpenID Connect Core and eight related specs as ISO/IEC 26131 to 26139.

OIDC uses the OAuth 2.0 authorization code flow and adds an ID token. The spec defines the ID token as "a security token that contains Claims about the Authentication of an End-User", in the form of a JSON Web Token (JWT). Every ID token must carry the issuer (iss), the user's identifier (sub), the audience (aud), an expiry time (exp), and the time it was issued (iat).

OpenID Connect authorization code flow with PKCE in seven steps: the app redirects the browser to /authorize with a code challenge, the browser goes to the OpenID provider, the user signs in and consents, the provider redirects back with a code, the browser hands the code to the app, the app exchanges the code and verifier at /token, and the provider returns an ID token and an access token.

Four things make OIDC easier to work with than SAML.

  • Tokens stay out of the redirects. The code flow "returns an Authorization Code to the Client, which can then exchange it for an ID Token and an Access Token directly". The redirect carries only the code, so the tokens never appear in a URL.
  • OIDC uses JSON and JWTs instead of XML. Every language has a JWT library, and your app checks one signature on a compact token.
  • Clients can discover the configuration. A provider publishes its endpoints and keys at /.well-known/openid-configuration. An enterprise connection often needs only an issuer URL, a client ID, and a secret.
  • OIDC works for mobile apps and single-page apps. With PKCE, a public client, which cannot keep a secret, can still use the code flow.

"Sign in with Google" uses OIDC. Google says that its OAuth 2.0 implementation for authentication "conforms to the OpenID Connect specification, and is OpenID Certified".

How OAuth 2.0 works

RFC 6749 defines OAuth 2.0 as a framework that "enables a third-party application to obtain limited access to an HTTP service", either for a user or for itself. The result is an access token, usually sent as a bearer token. The bearer token spec warns that "any party in possession of a bearer token" can use it.

These are the grants to use in 2026:

GrantUse it forStatus
Authorization code with PKCEWeb, mobile, and single-page apps that act for a user, third-party integrations, AI agents, and MCP clientsRecommended. "Public clients MUST use PKCE"
Client credentialsBackend services and jobs that call an API with no user presentCurrent
Device authorizationTVs, CLIs, and devices without a browser or keyboardCurrent
ImplicitNothing new"SHOULD NOT" be used. Removed in OAuth 2.1
Resource owner passwordNothing"MUST NOT be used". Removed in OAuth 2.1

The statuses come from RFC 9700, the IETF's current security advice for OAuth 2.0.

OAuth 2.1 collects these rules into one document. It is still an IETF draft. Version 17 came out in October 2026, and the working group plans to send it to the IESG, the group that approves IETF standards, in December 2026. OAuth 2.1 requires PKCE for the authorization code grant, drops the implicit and password grants, requires exact redirect URI matching, and forbids bearer tokens in query strings. If your provider already follows RFC 9700, little changes for you.

Don't use an OAuth access token as proof of login. A provider issues an access token for one API, and only that API should read it. Get the user's identity from an OIDC ID token or a SAML assertion, and check its issuer and audience. This mistake is the main reason OIDC exists.

SAML vs OIDC for enterprise SSO: support both

Most B2B teams face this choice. Microsoft's decision guide puts it this way: "OIDC suits new, cloud-native SaaS and customers with modern identity, while SAML is a requirement-driven choice for enterprise customers, compliance or procurement mandates, or legacy identity providers that support only SAML". Its advice is "If unsure, default to OIDC for new SaaS development".

The large identity providers support both protocols. The Microsoft Entra app gallery has separate SAML and OIDC tracks for listed apps. Okta supports OAuth 2.0 and OIDC as well as SAML 2.0 app integrations. Google Workspace lets admins add custom SAML apps.

Your customer's IT team makes the decision. If that team accepts only SAML, you need SAML to win the customer. In a 2025 Okta survey of 1,000 enterprises, 96% of technology buyers put identity and access requirements in their requests for proposals (RFPs) for SaaS. In practice, that means three steps:

  1. Build your own login on OIDC, even before you have enterprise customers.
  2. Offer SAML and OIDC enterprise connections for each customer organization once you sell to companies. Don't build SAML yourself. Every provider below handles the XML, the certificates, and the metadata.
  3. Add SCIM when customers ask for automatic provisioning and deprovisioning. SCIM 2.0 is a separate protocol that manages user accounts across domains. SSO signs users in, and SCIM creates and removes their accounts.

Most auth providers support SAML, half support SCIM

Our directory tracks 55 features across 37 auth providers. The chart shows how many providers support each protocol feature from this post.

Protocol support across 37 auth providers

Number of providers in the Auth0Alternatives directory that support each feature, November 2026

  • Enterprise SSO34
  • SAML33
  • Access tokens32
  • M2M tokens28
  • MCP auth24
  • SCIM18
  • Device login18
  • LDAP13

Source: Auth0Alternatives listings

Show data
Providers (of 37)
Enterprise SSO34
SAML33
Access tokens32
M2M tokens28
MCP auth24
SCIM18
Device login18
LDAP13

Download this chart

You're welcome to use it in articles, reports and presentations. In return, please credit Auth0Alternativeswith a link to the article it comes from.

Attribution to use with the chart

Source: <a href="https://www.auth0alternatives.com/blog/saml-vs-oidc-vs-oauth">Auth0Alternatives</a> by Auth0Alternatives

"M2M tokens" means the OAuth client credentials grant. Almost every provider supports SAML. SCIM separates them, and only 18 of the 37 providers support it. If your customers are enterprises, check for SCIM first. The feature pages for SAML and SCIM list every provider.

The table shows a selection of providers with SAML support, from our listings.

ProviderSAMLSCIMLDAPOpen sourceSelf-hosted
Auth0
Yes
Yes
Yes
No
No
WorkOS
Yes
Yes
No
No
No
Descope
Yes
Yes
Yes
No
No
Scalekit
Yes
Yes
No
No
No
Stytch
Yes
Yes
No
No
No
Frontegg
Yes
Yes
No
No
No
FusionAuth
Yes
Yes
Yes
No
Yes
Zitadel
Yes
Yes
Yes
Yes
Yes
Ory
Yes
Yes
Yes
Yes
Yes
authentik
Yes
Yes
Yes
Yes
Yes
Better Auth
Yes
Yes
No
Yes
Yes
Keycloak
Yes
No
Yes
Yes
Yes
Clerk
Yes
No
No
No
No
Amazon Cognito
Yes
No
No
No
No

To compare two providers side by side, see WorkOS vs Auth0 or Keycloak vs Zitadel.

Pick the protocol by what you build

You are buildingUse
Login for your own web or mobile appOIDC through an auth provider
Sign-in with Google, Microsoft, or GitHubOIDC, or OAuth 2.0 where a provider has no OIDC
SSO for employees of your business customersSAML and OIDC enterprise connections
Automatic user provisioning for those customersSCIM 2.0
A public API that other apps call for a userOAuth 2.0, authorization code with PKCE
An MCP server or tools for AI agentsOAuth 2.0, see providers with MCP authorization
Calls between your own servicesOAuth 2.0 client credentials
Login on a TV or in a CLIOAuth 2.0 device authorization

To compare vendors, start with Auth0 vs Okta. It explains which of the two products is for your customers and which is for your employees.

FAQ

No. OpenID Connect replaced the older OpenID 2.0. The OpenID Foundation says the two "solve a very similar set of problems". OpenID 2.0 "used XML and a custom message signature scheme", and OIDC uses OAuth 2.0 and JSON. Today, "OpenID" almost always means OIDC.

Yes. Many products use both. A typical B2B app signs employees in with SAML, then issues its own OAuth access tokens for its API. The two protocols solve different problems, so they don't conflict.

Neither is more secure by design. Both rely on signed tokens that your app checks. SAML's XML signatures have a long history of implementation bugs. OIDC inherits OAuth's pitfalls, and RFC 9700 lists those pitfalls in detail. The secure choice is a well-maintained implementation, not a particular protocol.

Both. Okta supports OAuth 2.0 and OIDC and lets admins create SAML 2.0 app integrations. Auth0, also owned by Okta, lists OAuth 2.0, OIDC, SAML, WS-Federation, LDAP, and SCIM among the standards it uses.

"Sign in with Google" uses OpenID Connect. Google Workspace can also act as a SAML identity provider for company apps.

Not yet. In November 2026, OAuth 2.1 is at draft 17, and the working group plans to submit it to the IESG in December 2026. Most of its rules already apply through RFC 9700.

Only if your customers ask for it. Consumer apps and self-serve B2B products usually don't need SAML. Once you sell to larger companies, expect some IT teams to require it. Pick an auth provider that offers both.

Share:

On this page

  1. SAML and OIDC handle authentication, OAuth handles authorization
  2. SAML vs OIDC vs OAuth compared
  3. How SAML works
  4. How OpenID Connect works
  5. How OAuth 2.0 works
  6. SAML vs OIDC for enterprise SSO: support both
  7. Most auth providers support SAML, half support SCIM
  8. Pick the protocol by what you build
  9. FAQ
Favicon

Β 

Β Β 
Β 
Subscribe to our newsletter

Join other CTOs and engineers to get the latest news and to keep your apps secure.

Browse:Open SourceSelf-hostedB2BB2CFeaturesComplianceData Residency
Quick Links:Contact UsSubmitBlogAbout Us
Built withDirstarter
Auth0Alternatives
FeaturesOpen SourceSelf-hostedB2BB2C
SubmitSign In

Discover

LatestOpen SourceSelf-hostedB2BB2CAll providers

AI & Agents

MCP AuthorizationAgent IdentitiesToken VaultAI Agent DetectionDevice LoginAll features

Data Residency

πŸ‡ͺπŸ‡ΊEuropean UnionπŸ‡ΊπŸ‡ΈUnited StatesπŸ‡¬πŸ‡§United KingdomπŸ‡¨πŸ‡­SwitzerlandπŸ‡¦πŸ‡ΊAustraliaAll regions

Compliance

SOC2GDPRISO 27001HIPAAPCI DSSAll compliance
Submit
Popular Auth0 Comparisons:
Engity vs Auth0
Amazon Cognito vs Auth0
Entra External ID vs Auth0
Firebase Authentication vs Auth0
Clerk vs Auth0
WorkOS vs Auth0
Frontegg vs Auth0
FusionAuth vs Auth0
Supabase Auth vs Auth0
Auth.js vs Auth0
Ory vs Auth0
SuperTokens vs Auth0
Logto vs Auth0
Hanko vs Auth0
Hexclave vs Auth0
Authress vs Auth0
Popular WorkOS Comparisons:
Engity vs WorkOS
Auth0 vs WorkOS
Amazon Cognito vs WorkOS
Entra External ID vs WorkOS
Firebase Authentication vs WorkOS
Clerk vs WorkOS
Frontegg vs WorkOS
FusionAuth vs WorkOS
Supabase Auth vs WorkOS
Auth.js vs WorkOS
Ory vs WorkOS
SuperTokens vs WorkOS
Logto vs WorkOS
Hanko vs WorkOS
Hexclave vs WorkOS
Authress vs WorkOS