October 24, 2007
OAuth 1.0 published
The OAuthAn authorization framework — lets apps access user data without sharing passwords. community finalized OAuthAn authorization framework — lets apps access user data without sharing passwords. Core 1.0 on October 24, 2007 — a protocol for delegated APIApplication programming interface — a defined way for programs to talk to each other or to a service. access without sharing passwords.
What it was for
OAuthAn authorization framework — lets apps access user data without sharing passwords. 1.0 let users grant third-party apps limited access to services like photos or tweets using signed requests instead of handing over credentials. Twitter, Flickr, and early social APIs adopted it. The three-legged dance (request token, authorize, access token) was clunky but proved delegated authorization could work at web scale — setting the stage for OAuthAn authorization framework — lets apps access user data without sharing passwords. 2.0 and OpenID ConnectAn identity layer on OAuth 2.0 — standardized login with ID tokens and user profiles..
Why it's here
OAuthAn authorization framework — lets apps access user data without sharing passwords. 1.0 was the first grassroots standard for APIApplication programming interface — a defined way for programs to talk to each other or to a service. delegation across competing web platforms.
Why it mattered
It established the consent-and-token model that modern identity federation still builds on.
What it solved
Apps needed user data from other services without storing passwords or getting full account control.
Media
- ImageOAuth
Chris Messina, CC BY-SA 3.0, via Wikimedia Commons
Related
- OAuth 2.0 standardizedOctober 2012
- OpenID Connect 1.0 publishedFebruary 25, 2014
- JWT standardizedMay 2015
- REST architectural style defined2000