RFC 6749 - The OAuth 2.0 Authorization Framework
The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. This specification replaces and obsoletes the OAuth 1.0 protocol described in RFC 5849. [STANDARDS-TRACK]
Internet Engineering Task Force (IETF) D. Hardt, Ed. Request for Comments: 6749 Microsoft Obsoletes: 5849 October 2012 Category: Standards Track ISSN: 2070-1721 Abstract The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. This specification replaces and obsoletes the OAuth 1.0 protocol described in RFC 5849. Status of This…
saved by
related reading
- RFC 9700: Best Current Practice for OAuth 2.0 Securitydatatracker.ietf.org
- What is OAuth 2.0? Definition & Examples | Auth0auth0.com
- Threat actors misuse OAuth applications to automate financially driven attacksmicrosoft.com
- RFC 6902 - JavaScript Object Notation (JSON) Patchdatatracker.ietf.org
- Signing in with Google - OAuth 2.0 Simplifiedoauth.com
- When MFA isn’t an option: The legacy of ROPC | Red Canaryredcanary.com
- Centralization and Internet Standardsietf.org
- RFC 7800 - Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)datatracker.ietf.org
- Auth | Supabase Docssupabase.com
- About authentication with a GitHub App - GitHub Docsdocs.github.com
- webauth:sec10.pdfpdos.csail.mit.edu
- RFC 9901 - Selective Disclosure for JSON Web Tokensdatatracker.ietf.org