OAuth vs OpenID Connect
OAuth 2.0 lets an app act for you without ever seeing your password, and OpenID Connect tells the app who you are. OAuth hands out access tokens, which say what an app may do. OpenID Connect sits on top of OAuth. It adds an ID token, which says who logged in. Use OpenID Connect to log people in, and OAuth for access.
OAuth 2.0
A standard that lets one app use your account in another. You never share your password.
OAuth 2.0 lets one app act for you in another, with no password. You click allow on a screen from the service that holds your data. That service then gives the app an access token with only the rights you agreed to. You can take those rights back at any time. It was published in 2012 and is how most apps link to each other today.
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
- OAuth 2.0
- A standard that lets one app use your account in another. You never share your password.
- OpenID Connect (OIDC)
- A login layer on top of OAuth 2.0. It tells an app who the user is.