Skip to main content
Definition Website Computer and Technology

Open Authorization

Subject: Computer and Technology noun /ˈoʊ.pən ˌɔː.θə.rəˈzeɪ.ʃən/ 1 definition

  1. Definition (noun)

    Entry #321 · Updated

    Open Authorization (OAuth) is an open standard and delegated access-control framework—most widely deployed as OAuth 2.0 (RFC 6749) and consolidated under OAuth 2.1—that enables a resource owner to grant third-party client applications limited, revocable access to protected HTTP resources without disclosing underlying credentials. Rather than embedding a user's password inside an external application, the protocol separates access negotiation across four distinct roles: the resource owner, the client application, the authorization server, and the resource server. After the authorization server authenticates the resource owner and records explicit consent for requested permission scopes, it issues short-lived, cryptographically signed or opaque access tokens—and optionally refresh tokens—that the client presents over TLS to call authorized APIs. By replacing shared static secrets with granular, time-bounded tokens, OAuth minimizes credential exposure and centralizes revocation across distributed services; however, it governs delegated authorization rather than user authentication, requiring an identity layer such as OpenID Connect (OIDC) when an application needs verified claims about who the end user is.

    Common Forms

    • Authorization Code Grant with PKCE: An interactive user-delegation flow for web, mobile, and single-page applications in which the authorization server returns a single-use code via browser redirect, and the client exchanges it alongside a Proof Key for Code Exchange (code_verifier) at a back-channel token endpoint to prevent code interception.

    • Client Credentials Grant: A machine-to-machine flow in which a confidential backend service or automated daemon authenticates directly using its own credentials—such as a client secret, signed JWT assertion, or mutual TLS certificate—to access APIs on behalf of the application itself rather than an end user.

    • Device Authorization Grant: An out-of-band flow designed for browserless or input-constrained hardware, such as smart TVs and CLI utilities, where the client displays a verification URI and short user code so the owner can approve scopes on a secondary device while the client polls for the token.

    • Refresh Token Grant: A non-interactive renewal exchange that lets a client trade a long-lived refresh token for a new short-lived access token when the original expires, frequently paired with single-use token rotation so stolen refresh tokens are immediately detected and revoked.

    Example

    A third-party reporting tool requests read-only access to a user's cloud calendar by redirecting their browser to https://auth.example.com/oauth2/authorize with response_type=code, scope=calendar.readonly, a state nonce, and a SHA-256 code_challenge. Once the user grants consent, the reporting backend exchanges the returned authorization code and its code_verifier via HTTPS POST to /oauth2/token for a 3,600-second Bearer JWT access token, which it passes in the Authorization: Bearer <token> header to fetch events from https://api.example.com/v1/calendars without ever receiving the user's password.