Protocols
Saved & recent

OAuth 2.0

Also called: OAuth, delegated authorization

OAuth 2.0 is a framework for obtaining limited access to protected resources. A client receives an access token from an authorization server and presents it to a resource server. In delegated access, a resource owner can authorize that client without giving it their account password.

For example, a calendar app might receive permission to read events without permission to delete them. Scopes and resource policy determine the access granted; the client does not automatically receive all account privileges. OAuth alone is not a standard login identity assertion: OpenID Connect supplies that identity layer.

Read first
Authorization
Related
OpenID Connect, Authorization code flow, Authorization, Refresh token, Token revocation
Further reading
RFC 6749 — The OAuth 2.0 Authorization Framework
owner / client app authorization server calendar API owner grants calendar read limited access token to app client presents access token sign-in at authorization server read calendar · allowed delete calendar · denied illustrative token scope
Illustrative delegated calendar access: the owner grants read access, the authorization server issues a limited token, and the client presents it to the calendar API. Resource policy permits reading but denies deletion; the token’s format is unspecified.

View in the full Protocols collection