IT Glossary
OpenID Connect (OIDC) adds an identity layer on top of OAuth 2.0. Learn how OIDC works, how it compares to SAML, and where it fits in modern SSO.
June 8, 2026
OpenID Connect (OIDC) is an authentication protocol built on top of OAuth 2.0. While OAuth 2.0 handles authorization, OIDC adds a standardized identity layer that lets an application verify who a user is and obtain basic profile information through an ID token. OIDC is widely used for modern web and mobile single sign-on, including consumer logins such as "Sign in with Google."
A SaaS product offers "Sign in with Google" through OIDC, so users authenticate with their existing Google identity instead of a new password. For IT, OIDC and SAML often coexist: newer tools speak OIDC, older enterprise apps speak SAML. Governance has to span both, plus the apps that support neither.
OAuth 2.0 grants authorization to resources. OIDC sits on top of it and adds authentication, telling the app who the user is.
Not entirely. OIDC leads for modern and mobile apps, while SAML stays dominant across established enterprise web applications. Most companies run both.
A signed JSON Web Token issued by the IdP that proves the user's identity to the application.
Corma governs access whether your apps use OIDC, SAML, or neither. Explore Corma for IT teams or request a demo.