SAML vs OpenID Connect
People think SAML and OpenID Connect do different jobs, and they do the same one. Both let one login open many apps. SAML is older and sends a signed XML note through the browser. OpenID Connect is newer, sends a signed JSON token, and suits phone apps and APIs. Most work apps take both.
Security Assertion Markup Language (SAML)
An XML standard for single sign-on. A signed note tells the app who you are.
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.
OpenID Connect (OIDC)
A login layer on top of OAuth 2.0. It tells an app who the user is.
OpenID Connect is a layer on top of OAuth 2.0 that adds logging in. OAuth on its own only grants access to data. OpenID Connect also hands the app an ID token, a JWT that says who the user is. Sign in with Google and Sign in with Microsoft both use it. It was finished in 2014.
In one line
- Security Assertion Markup Language (SAML)
- An XML standard for single sign-on. A signed note tells the app who you are.
- OpenID Connect (OIDC)
- A login layer on top of OAuth 2.0. It tells an app who the user is.