February 25, 2014
OpenID Connect 1.0 published
The OpenID Foundation published OpenID ConnectAn identity layer on OAuth 2.0 — standardized login with ID tokens and user profiles. Core 1.0 on February 25, 2014 — an identity layer on top of OAuthAn authorization framework — lets apps access user data without sharing passwords. 2.0 for login and profile sharing.
What it was for
OpenID ConnectAn identity layer on OAuth 2.0 — standardized login with ID tokens and user profiles. adds ID tokens (JWTs), a UserInfo endpoint, and standardized scopes to OAuthAn authorization framework — lets apps access user data without sharing passwords. — `Sign in with Google` flows use it under the hood. Relying parties verify issuer, audience, and signature instead of inventing login protocols. Example: exchange an authorization code for an ID token containing `sub`, `email`, and `name` claims.
Why it's here
OpenID ConnectAn identity layer on OAuth 2.0 — standardized login with ID tokens and user profiles. standardized federated login on the OAuthAn authorization framework — lets apps access user data without sharing passwords. 2.0 foundation.
Why it mattered
It replaced proprietary social-login hacks with interoperable identity tokens across providers.
What it solved
OAuthAn authorization framework — lets apps access user data without sharing passwords. 2.0 alone did not define how to authenticate users or share profile data securely.
Media
- ImageOpenID
Randy Reddig (ydnar) [2], Public domain, via Wikimedia Commons
Related
- OAuth 2.0 standardizedOctober 2012
- JWT standardizedMay 2015
- TLS 1.0 standardizedJanuary 1999