OAuth 2.0

OAuth 2.0 is the industry-standard protocol for authorization. OAuth 2.0 focuses on client developer simplicity while providing specific authorization flows for web applications, desktop applications, mobile phones, and living room devices. This specification and its extensions are being developed within the IETF OAuth Working Group .

OAuth 2.1 is an in-progress effort to consolidate OAuth 2.0 and many common extensions under a new name.

Questions, suggestions and protocol changes should be discussed on the mailing list .

OAuth 2.0

• OAuth 2.0 Framework - RFC 6749
  • Access Tokens
  • Refresh Tokens
  • OAuth Scope
• OAuth Grant Types
  • Authorization Code
  • PKCE
  • Client Credentials
  • Device Code
  • Refresh Token
  • Legacy: Implicit Flow
  • Legacy: Password Grant
• Client Types - Confidential and Public Applications
• Client Authentication
• Bearer Tokens - RFC 6750
• Threat Model and Security Considerations - RFC 6819
• OAuth Security Best Current Practice
• ID Tokens vs Access Tokens

Mobile and Other Devices

• Native Apps - Recommendations for using OAuth with native apps
• Browser-Based Apps - Recommendations for using OAuth with browser-based apps (e.g. an SPA)
• Device Authorization Grant - OAuth for devices with no browser or no keyboard

Token and Token Management

• JWT Profile for Access Tokens - RFC 9068, a standard for structured access tokens
• Token Introspection - RFC 7662, to determine the active state and meta-information of a token
• Token Revocation - RFC 7009, to signal that a previously obtained token is no longer needed
• JSON Web Token - RFC 7519
• Token Exchange - RFC 8693

Discovery and Registration

• Authorization Server Metadata - RFC 8414, for clients to discover OAuth endpoints and authorization server capabilities
• Dynamic Client Registration - RFC 7591, to programmatically register OAuth clients
• Dynamic Client Registration Management - Experimental RFC 7592, for updating and managing dynamically registered OAuth clients

High Security OAuth

These specs are used to add additional security properties on top of OAuth 2.0.

• Pushed Authorization Requests (PAR) - RFC 9126
• Demonstration of Proof of Possession (DPoP) - RFC 9449
• Mutual TLS - RFC 8705
• Private Key JWT - (RFC 7521, RFC 7521, OpenID)
• FAPI

Experimental and Draft Specs

The specs below are either experimental or in draft status and are still active working group items. They will likely change before they are finalized as RFCs or BCPs.

• Incremental Authorization
• Step-up Authentication Challenge
• All OAuth Working Group Documents

Additional Extensions

• OAuth Extension Parameter Registry
• OAuth Assertions Framework - RFC 7521
• SAML2 Bearer Assertion - RFC 7522, for integrating with existing identity systems
• JWT Bearer Assertion - RFC 7523
• Authorization Server Issuer Identification - RFC 9207, indicates the authorization server identifier in the authorization response
• Rich Authorization Requests (RAR) - RFC 9396

Related Work from Other Communities

• FAPI (OpenID Foundation)
• WebAuthn - Web Authentication
• passkeys are a new way to sign in to services without a password
• HTTP Message Signatures - A generic HTTP message signing spec
• OpenID for Verifiable Credentials

Community Resources

• OAuth 2.0 Simplified
• Books about OAuth
  • OAuth 2.0 Simplified by Aaron Parecki
  • OAuth 2 in Action by Justin Richer and Antonio Sanso
  • Mastering OAuth 2.0 by Charles Bihis
  • OAuth 2.0 Cookbook by Adolfo Eloy Nascimento
• The Nuts and Bolts of OAuth - video course by Aaron Parecki

Protocols Built on OAuth 2.0

• OpenID Connect (OpenID Foundation)
• UMA 2.0 (Kantara)
• IndieAuth (W3C)

Code and Services

• OAuth 2.0 Code and Services

OAuth 2.1

• OAuth 2.1 - An in-progress update to consolidate and simplify OAuth 2.0
• It's Time for OAuth 2.1 (by Aaron Parecki)

Legacy

• OAuth 1.0 and 1.0a