Skip to content
ecdsa.com

OAuth 2.0

The authorization framework of RFC 6749 (2012) in which an authorization server issues access tokens to clients so they can call APIs with delegated, scoped permissions instead of user passwords.
Also written asOAuthOAuth2RFC 6749OAuth 2.1

Roles: resource owner, client, authorization server and resource server. The authorization code grant (with PKCE) is the main user-facing flow; client credentials covers service-to-service calls; the device authorization grant (RFC 8628) covers TVs and CLIs; refresh tokens renew access. OAuth is about authorization; OpenID Connect adds authentication on top.

RFC 9700, the OAuth 2.0 Security Best Current Practice (January 2025), retires the implicit grant and the resource owner password grant, requires PKCE for public clients and recommends it for all, demands exact redirect URI matching and recommends sender-constrained tokens. The OAuth 2.1 Internet-Draft consolidates those rules but was not yet an RFC in October 2026.

Standards and references

All terms