Skip to content
Okta vs Entra

Reviewed 10 November 2026

How single sign-on works: SAML, OpenID Connect and the identity provider

Reviewed 2026-11-10 · Editorial assessment by the editors

By the editors · 3 min read

In single sign-on the user authenticates once at an identity provider, which then vouches for them to each application with a signed message. SAML sends an XML assertion; OpenID Connect sends a signed ID token on top of OAuth 2.0. Applications trust the signature, so the key that makes it is the most valuable secret in the setup.

What happens during an SSO sign-in?

A user opens an application. The application does not check a password itself; it sends the user to the identity provider (IdP) it trusts, such as Okta, Microsoft Entra ID or Ping Identity. The IdP authenticates the user, applies its sign-in policy, such as which MFA factor is required, and sends the user back with a signed statement of who they are. The application checks the signature and starts a session.

When the user opens a second application, the round trip repeats, but the user already has a session at the IdP, so there is no second password prompt. That is the "single" in single sign-on.

How do SAML and OpenID Connect differ?

SAML 2.0 is an XML-based standard in which the IdP sends a signed assertion to the application. It is widely used for enterprise SaaS. OpenID Connect is an identity layer on OAuth 2.0: the application receives a signed ID token, and can also obtain access tokens to call APIs, which is why it is common for modern web and mobile apps.

Most identity providers support both. Microsoft lists SAML, OpenID Connect, password-based and linked SSO for apps in the Entra gallery. Okta's Microsoft 365 integration lists SAML, SWA, WS-Federation and OpenID Connect.

Why does the signing key matter?

Every assertion and ID token is signed with the IdP's key, and applications accept any message that carries a valid signature. A stolen key lets an attacker forge sign-ins for any user, the attack known as Golden SAML. That is why NIST IR 8587, finalised on 15 September 2026, concentrates on key management and token verification. The lesson on tokens and signing keys goes further.

What does single sign-on not do on its own?

Single sign-on decides how a user signs in to each app. It does not create the user's account inside that app, which is a separate job usually done over SCIM, and both Okta and Entra ID support it. Deciding when to ask for a stronger factor is a third layer: Conditional Access in Entra ID, Adaptive MFA in Okta. The next lessons take catalogs, directories and policy one at a time.

Where does this matter on this site?

The single sign-on comparison calls Okta and Entra ID on app catalog, protocols and Microsoft 365 sign-in.

Next lesson: App catalogs