The OAuth 2.1 Authorization Framework

The OAuth 2.1 Authorization Framework Hellō

dick.hardt@gmail.com

Okta

aaron@parecki.com https://aaronparecki.com

SPRIND

torsten@lodderstedt.net

Security OAuth Working Group Internet-Draft The OAuth 2.1 authorization framework enables an application to obtain limited access to a protected resource, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and an authorization service, or by allowing the application to obtain access on its own behalf. This specification replaces and obsoletes the OAuth 2.0 Authorization Framework described in RFC 6749 and the Bearer Token Usage in RFC 6750. Discussion Venues Discussion of this document takes place on the OAuth Working Group mailing list (oauth@ietf.org), which is archived at . Source for this draft and an issue tracker can be found at .

Introduction OAuth introduces an authorization layer to the client-server authentication model by separating the role of the client from that of the resource owner. In OAuth, the client requests access to resources controlled by the resource owner and hosted by the resource server. Instead of using the resource owner's credentials to access protected resources, the client obtains an access token -- a credential representing a specific set of access attributes such as scope and lifetime. Access tokens are issued to clients by an authorization server with the approval of the resource owner. The client uses the access token to access the protected resources hosted by the resource server. In the older, more limited client-server authentication model, the client requests an access-restricted resource (protected resource) on the server by authenticating to the server using the resource owner's credentials. In order to provide applications access to restricted resources, the resource owner shares their credentials with the application. This creates several problems and limitations:

Applications are required to store the resource owner's credentials for future use, typically a password in cleartext.
Servers are required to support password authentication, despite the security weaknesses inherent in passwords.
Applications gain overly broad access to the resource owner's protected resources, leaving resource owners without any ability to restrict duration or access to a limited subset of resources.
Resource owners often reuse passwords with other unrelated services, despite best security practices. This password reuse means a vulnerability or exposure in one service may have security implications in completely unrelated services.
Resource owners cannot revoke access to an individual application without revoking access to all third parties, and must do so by changing their password.
Compromise of any application results in compromise of the end-user's password and all of the data protected by that password.

For example, using OAuth, an end-user (resource owner) can grant a financial management service (client) access to their sensitive transaction history stored at a banking service (resource server) without sharing their username and password with the financial management service. Instead, the end-user authenticates directly with their financial institution's server (authorization server), which issues the financial management service delegation-specific credentials (access token). This separation of concerns also provides the ability to use more advanced user authentication methods such as multi-factor authentication and even passwordless authentication, without any modification to the applications. With all user authentication logic handled by the authorization server, applications don't need to be concerned with the specifics of implementing any particular authentication mechanism. This provides the ability for the authorization server to manage the user authentication policies and even change them in the future without coordinating the changes with applications. The authorization layer can also simplify how a resource server determines whether a request is authorized. Traditionally, after authenticating the client, each resource server would evaluate policies to determine whether the client is authorized on each API call. In a distributed system, the policies need to be synchronized to all the resource servers, or the resource server must call a central policy server to process each request. In OAuth, evaluation of the policies is performed only when a new access token is created by the authorization server. If the authorized access is represented in the access token, the resource server no longer needs to evaluate the policies, and only needs to validate the access token. This simplification applies when the application is acting on behalf of a resource owner, or on behalf of itself. OAuth is an authorization protocol, not an authentication protocol, as OAuth does not define the necessary components to achieve user authentication. An authentication protocol is necessary if the goal is to authenticate users. An example is OpenID Connect , which builds on OAuth to provide the security characteristics and necessary components required of an authentication protocol. The access token represents the authorization granted to the client. It is a common practice for the client to present the access token to a proprietary API that returns a user identifier for the resource owner, and then to use the result of the API as a proxy for authenticating the user. This practice is not part of the OAuth standard or security considerations, and may not have been considered by the resource owner. Implementers should carefully consult the documentation of the resource server before adopting this practice. This specification is designed for use with HTTP . The use of OAuth over any protocol other than HTTP is out of scope. Since the publication of the OAuth 2.0 Authorization Framework in October 2012, it has been updated by OAuth 2.0 for Native Apps , OAuth Security Best Current Practice , and OAuth 2.0 for Browser-Based Applications . The OAuth 2.0 Authorization Framework: Bearer Token Usage has also been updated by . This Standards Track specification consolidates the information in all of these documents and removes features that have been found to be insecure in .

Roles OAuth defines four roles:

"resource owner":: An entity capable of granting access to a protected resource. When the resource owner is a person, it is referred to as an end-user. This is sometimes abbreviated as "RO".
"resource server":: The server hosting the protected resources, capable of accepting and responding to protected resource requests using access tokens. The resource server is often accessible via an API. This is sometimes abbreviated as "RS".
"client":: An application making protected resource requests on behalf of the resource owner and with its authorization. The term "client" does not imply any particular implementation characteristics (e.g., whether the application executes on a server, a desktop, or other devices).
"authorization server":: The server issuing access tokens to the client after successfully authenticating the resource owner and obtaining authorization. This is sometimes abbreviated as "AS".

Most of this specification defines the interaction between the client and the authorization server, as well as between the client and the resource server. The interaction between the authorization server and resource server is beyond the scope of this specification; however, several extensions have been defined to provide an option for interoperability between resource servers and authorization servers. The authorization server may be the same server as the resource server or a separate entity. A single authorization server may issue access tokens accepted by multiple resource servers. The interaction between the resource owner and authorization server (e.g., how the end-user authenticates themselves at the authorization server) is also out of scope for this specification, with some exceptions, such as security considerations around prompting the end-user for consent. When the resource owner is the end-user, the user will interact with the client. When the client is a web-based application, the user will interact with the client through a user agent (as described in ). When the client is a native application, the user will interact with the client directly through the operating system. See for further details.

Protocol Flow

Abstract Protocol Flow | | | | | | | |<-(3)-- Authorization Grant ---| | | | | Authorization | | |--(4)-- Authorization Grant -->| Server | | Client | | | | |<-(5)----- Access Token -------| | | | +---------------+ | | | | +---------------+ | |--(6)----- Access Token ------>| Resource | | | | Server | | |<-(7)--- Protected Resource ---| | +--------+ +---------------+ ]]> The abstract OAuth 2.1 flow illustrated in describes the interaction between the four roles and includes the following steps:

The client requests authorization from the resource owner via the authorization server, which acts as an intermediary between the client and the resource owner.
The resource owner approves the request.
The client receives an authorization grant, which is a credential representing the resource owner's authorization, expressed using one of the authorization grant types defined in this specification or using an extension grant type. The authorization grant type depends on the method used by the client to request authorization and the types supported by the authorization server.
The client requests an access token by authenticating with the authorization server and presenting the authorization grant.
The authorization server authenticates the client and validates the authorization grant, and if valid, issues an access token.
The client requests the protected resource from the resource server by presenting the access token.
The resource server validates the access token, and if valid, serves the request.

The authorization code grant, which uses the authorization server as an intermediary to obtain the resource owner's authorization, is illustrated in in . Some extensions begin with a direct request from the client to the authorization server before any interaction with the resource owner, such as Pushed Authorization Requests and the Device Authorization Grant . See for these and other extensions.

Authorization Grant An authorization grant represents the resource owner's authorization (to access its protected resources) used by the client to obtain an access token. This specification defines three grant types -- authorization code, refresh token, and client credentials -- as well as an extensibility mechanism for defining additional types.

Authorization Code An authorization code is a temporary credential used to obtain an access token. Instead of the client requesting authorization directly from the resource owner, the client directs the resource owner to an authorization server (via its user agent), which in turn directs the resource owner back to the client with the authorization code. The client can then exchange the authorization code for an access token. Before directing the resource owner back to the client with the authorization code, the authorization server authenticates the resource owner, and may request the resource owner's consent or otherwise inform them of the client's request. Because the resource owner only authenticates with the authorization server, the resource owner's credentials are never shared with the client, and the client does not need to have knowledge of any additional authentication steps such as multi-factor authentication or delegated accounts. The authorization code provides a few important security benefits, such as the ability to authenticate the client, as well as the transmission of the access token directly to the client without passing it through the resource owner's user agent and potentially exposing it to others, including the resource owner.

Refresh Token Refresh tokens are credentials used to obtain access tokens. Refresh tokens may be issued to the client by the authorization server and are used to obtain a new access token when the current access token becomes invalid or expires, or to obtain additional access tokens with identical or narrower scope (access tokens may have a shorter lifetime and fewer privileges than authorized by the resource owner). Issuing a refresh token is optional and at the discretion of the authorization server, which may issue one based on properties of the client, properties of the request, policies within the authorization server, or any other criteria. If the authorization server issues a refresh token, it is included when issuing an access token (i.e., step (2) in ). The lifetime of the refresh token is also at the discretion of the authorization server. A refresh token is a string representing the authorization granted to the client by the resource owner. The string is considered opaque to the client. The refresh token may be an identifier used to retrieve the authorization information or may encode this information into the string itself. Unlike access tokens, refresh tokens are intended for use only with authorization servers and are never sent to resource servers.

Refreshing an Expired Access Token | | | | | | | |<-(2)----------- Access Token -------------| | | | & Refresh Token | | | | | | | | +----------+ | | | |--(3)---- Access Token ---->| | | | | | | | | | | |<-(4)- Protected Resource --| Resource | | Authorization | | Client | | Server | | Server | | |--(5)---- Access Token ---->| | | | | | | | | | | |<-(6)- Invalid Token Error -| | | | | | +----------+ | | | | | | | |--(7)----------- Refresh Token ----------->| | | | | | | |<-(8)----------- Access Token -------------| | +--------+ & Optional Refresh Token +---------------+ ]]> The flow illustrated in includes the following steps:

The client requests an access token by authenticating with the authorization server and presenting a previously-obtained authorization grant.
The authorization server authenticates the client and validates the authorization grant, and if valid, issues an access token and optionally a refresh token.
The client makes a protected resource request to the resource server by presenting the access token.
The resource server validates the access token, and if valid, serves the request.
Steps (3) and (4) repeat until the access token expires. If the client knows the access token has expired, it skips to step (7); otherwise, it makes another protected resource request.
Since the access token is invalid, the resource server returns an invalid token error.
The client requests a new access token by presenting the refresh token and providing client authentication if it has been issued credentials. The client authentication requirements are based on the client type and on the authorization server policies.
The authorization server authenticates the client and validates the refresh token, and if valid, issues a new access token (and, optionally, a new refresh token).

If the refresh token expires, the client's only recourse is to initiate a new flow to obtain a new access token and refresh token. The authorization server might choose to use dynamic lifetimes (e.g., the refresh token expiry is extended as long as the refresh token is used at least once every 7 days), or the authorization server might revoke the refresh token before its scheduled expiration date for any reason, such as if the user revokes the application's access. This means the client already has to handle the case of a refresh token expiring at an arbitrary time.

Client Credentials The client credentials or other forms of client authentication (e.g., a private key used to sign a JWT, as described in and its update ) can be used as an authorization grant when the authorization scope is limited to the protected resources under the control of the client, or to protected resources previously arranged with the authorization server. Client credentials are used when the client is requesting access to protected resources based on an authorization previously arranged with the authorization server.

Access Token Access tokens are credentials used to access protected resources. An access token is a string representing an authorization issued to the client. The string is considered opaque to the client, even if it has a structure. The client MUST NOT expect to be able to parse the access token value. The authorization server is not required to use a consistent access token encoding or format other than what is expected by the resource server. The access granted by the resource owner to the client is represented by the access token created by the authorization server. Access tokens are short-lived to limit the impact of a leaked access token. The expiration of the access token is set by the authorization server. Depending on the authorization server implementation, the token string may be used by the resource server to retrieve the authorization information, or the token may self-contain the authorization information in a verifiable manner (e.g., a token string consisting of a signed data payload). One example of a token retrieval mechanism is Token Introspection , in which the RS calls an endpoint on the AS to validate the token presented by the client. One example of a structured token format is the JWT Profile for Access Tokens , a method of encoding and signing access token data as a JSON Web Token . Additional authentication credentials, which are beyond the scope of this specification, may be required in order for the client to use an access token. Such tokens are typically referred to as sender-constrained access tokens; examples include DPoP and Mutual TLS Certificate-Bound Access Tokens . The access token provides an abstraction layer, replacing different authorization constructs (e.g., username and password) with a single token understood by the resource server. This abstraction enables issuing access tokens more restrictive than the authorization grant used to obtain them, as well as removing the resource server's need to understand a wide range of authentication methods. Access tokens can have different formats, structures, and methods of utilization (e.g., cryptographic properties) based on the resource server security requirements. Access token attributes and the methods used to access protected resources may be extended beyond what is described in this specification. Access tokens (as well as any confidential access token attributes) MUST be kept confidential in transit and storage, and only shared among the authorization server, the resource servers for which the access token is valid, and the client to which the access token is issued. The authorization server MUST ensure that access tokens cannot be generated, modified, or guessed to produce valid access tokens by unauthorized parties.

Access Token Scope Access tokens are intended to be issued to clients with fewer privileges than those held by the user granting the access. This is known as a limited "scope" access token. The authorization server and resource server can use this scope mechanism to limit what types of resources or level of access a particular client can have. For example, a client may only need "read" access to a user's resources, but doesn't need to update resources, so the client can request the read-only scope defined by the authorization server and obtain an access token that cannot be used to update resources. This requires coordination between the authorization server, resource server, and client. The authorization server provides the client the ability to request specific scopes, and associates those scopes with the access token issued to the client. The resource server is then responsible for enforcing scopes when presented with a limited-scope access token. OAuth does not define any scope values; instead, scopes are defined by the authorization server or by extensions or profiles of OAuth. One such extension that defines scopes is , which defines a set of scopes that provide granular access to a user's profile information. It is recommended to avoid defining custom scopes that conflict with scopes from known extensions. To request a limited-scope access token, the client uses the scope request parameter at the authorization or token endpoints, depending on the grant type used. In turn, the authorization server uses the scope response parameter to inform the client of the scope of the access token issued. The value of the scope parameter is expressed as a space-delimited set of case-sensitive strings. The strings are defined by the authorization server. If the value contains multiple space-delimited strings, their order does not matter, and each string adds an additional access range to the requested scope. The authorization server MAY fully or partially ignore the scope requested by the client, based on the authorization server policy or the resource owner's instructions. If the issued access token scope is different from the one requested by the client, the authorization server MUST include the scope response parameter in the token response () to inform the client of the actual scope granted. If the client omits the scope parameter when requesting authorization, the authorization server MUST either process the request using a predefined default value or fail the request indicating an invalid scope. The authorization server SHOULD document its scope requirements and default value (if defined). Whether the scope of a grant is limited to what the resource owner approved in the corresponding authorization request, or also includes scopes the resource owner previously authorized for the same client, is determined by authorization server policy.

Bearer Tokens A bearer token is a security token with the property that any party in possession of the token (a "bearer") can use the token in any way that any other party in possession of it can. Using a bearer token does not require a bearer to prove possession of cryptographic key material (proof-of-possession). Bearer tokens may be enhanced with proof-of-possession specifications such as DPoP and mTLS to provide proof-of-possession characteristics. To protect against access token disclosure, the communication between the client and the resource server MUST utilize confidentiality and integrity protection as described in . There is no requirement on the particular structure or format of a bearer token. If a bearer token is a reference to authorization information, such references MUST be infeasible for an attacker to guess, for example, by using a sufficiently long cryptographically random string. If a bearer token uses an encoding mechanism to contain the authorization information in the token itself, the access token MUST use integrity protection sufficient to prevent the token from being modified. One example of an encoding and signing mechanism for access tokens is described in the JSON Web Token Profile for Access Tokens .

Sender-Constrained Access Tokens A sender-constrained access token binds the use of an access token to a specific sender. This sender is obliged to demonstrate knowledge of a certain secret as a prerequisite for the acceptance of that access token at the recipient (e.g., a resource server). Authorization and resource servers SHOULD use mechanisms for sender-constraining access tokens, such as OAuth 2.0 Demonstrating Proof of Possession (DPoP) or Mutual TLS for OAuth 2.0 . See for guidance on preventing misuse of stolen and leaked access tokens. It is RECOMMENDED to use end-to-end TLS between the client and the resource server. If TLS traffic needs to be terminated at an intermediary, refer to for further security advice.

Communication Security Implementations MUST use a mechanism to provide communication authentication, integrity, and confidentiality, such as Transport Layer Security (TLS) , to protect the exchange of cleartext credentials and tokens either in the content or in header fields from eavesdropping, which enables replay (e.g., see , , , and ). All OAuth protocol URLs (URLs exposed by the AS, RS, and client) MUST use the https scheme except for loopback interface redirect URIs, which MAY use the http scheme. When using https, TLS certificates MUST be checked according to . At the time of this writing, TLS version 1.3 is the most recent version. Implementations MAY also support additional transport-layer security mechanisms that meet their security requirements. The identification of the TLS versions and algorithms is outside the scope of this specification. Refer to for up-to-date recommendations on transport layer security, and to the relevant specifications for certificate validation and other security considerations.

HTTP Redirections This specification makes extensive use of HTTP redirections, in which the client or the authorization server directs the resource owner's user agent to another destination. While the examples in this specification show the use of the 302 (Found) status code, any other method available via the user agent to accomplish this redirection, with the exception of the 307 (Temporary Redirect) status code, is allowed and is considered to be an implementation detail. See for details.

Interoperability OAuth 2.1 provides a rich authorization framework with well-defined security properties. This specification leaves a few required components partially or fully undefined (e.g., client registration, authorization server capabilities, endpoint discovery). Some of these behaviors are defined in optional extensions that implementations can choose to use, such as:

: Authorization Server Metadata, defining an endpoint clients can use to look up the information needed to interact with a particular OAuth server
: Dynamic Client Registration, providing a mechanism for programmatically registering clients with an authorization server
: Dynamic Client Management, providing a mechanism for updating dynamically registered client information
: Token Introspection, defining a mechanism for resource servers to obtain information about access tokens

Please refer to for a list of extensions known at the time of publication.

Value Sizes This specification does not define a maximum length for the client_id, authorization codes, access tokens, refresh tokens, or most other protocol parameters, as the length of these values depends on implementation choices made by the party that issues them. In practice, implementations impose their own limits, and a value that exceeds the limit of a receiving implementation will cause the request to fail. Implementations MUST NOT assume that a value they receive fits within a particular length. The party that issues a value SHOULD document its length, and SHOULD take into account the limits of the components that will carry it. In particular, values returned in a redirect, such as the authorization code and state, are carried in a URI query string, and HTTP implementations commonly limit the length of the request-line and of individual header fields ( and ). Implementations SHOULD support parameter values long enough that requests remain within the 8000-octet request-line length recommended by . Resource servers in particular should not impose small limits on the length of access tokens, as tokens in a structured format, such as those defined by , routinely exceed one kilobyte.

Compatibility with OAuth 2.0 OAuth 2.1 is compatible with OAuth 2.0 with the extensions and restrictions from known best current practices applied. Specifically, features not specified in OAuth 2.0 core, such as PKCE, are required in OAuth 2.1. Additionally, some features available in OAuth 2.0, such as the Implicit or Resource Owner Password Credentials grant types, are not specified in OAuth 2.1. Furthermore, some behaviors allowed in OAuth 2.0 are restricted in OAuth 2.1, such as the strict string matching of redirect URIs required by OAuth 2.1. An authorization server can support both OAuth 2.0 and OAuth 2.1 clients. Which rules apply to a given client is determined by the authorization server's configuration for that client, for example as part of client registration (). This allows an authorization server to move existing clients to OAuth 2.1 one at a time. This specification does not define a way for a client or authorization server to signal which version it implements. See for more details on the differences from OAuth 2.0.

Notational Conventions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. This specification uses the Augmented Backus-Naur Form (ABNF) notation of . Additionally, the rule URI-reference is included from "Uniform Resource Identifier (URI): Generic Syntax" . Certain security-related terms are to be understood in the sense defined in . These terms include, but are not limited to, "attack", "authentication", "authorization", "certificate", "confidentiality", "credential", "encryption", "identity", "sign", "signature", "trust", "validate", and "verify". The term "content" is to be interpreted as described in . The term "user agent" is to be interpreted as described in . Unless otherwise noted, all the protocol parameter names and values are case sensitive.

Client Registration Before initiating the protocol, the client must have established an identifier () at the authorization server. The means through which the client identifier is established with the authorization server are beyond the scope of this specification, but typically involve either the client developer manually registering the client at the authorization server's website (after creating an account and agreeing to the service's Terms of Service) or the use of Dynamic Client Registration . Extensions may also define other programmatic methods of establishing client registration. Client registration does not require a direct interaction between the client and the authorization server. When supported by the authorization server, registration can rely on other means for establishing trust and obtaining the required client properties (e.g., redirect URI, client type). For example, registration can be accomplished using a self-issued or third-party-issued assertion, or by the authorization server performing client discovery using a trusted channel. Client registration MUST include:

the client type as described in ,
client details needed by the grant type in use, such as redirect URIs as described in , and
any other information required by the authorization server (e.g., application name, website, description, logo image, the acceptance of legal terms).

Dynamic Client Registration defines a common general data model for clients that may be used even with manual client registration.

Client Types OAuth 2.1 defines two client types based on their ability to authenticate securely with the authorization server.

"confidential":: Clients that have credentials with the AS are designated as "confidential clients".
"public":: Clients without credentials are called "public clients".

Any client with credentials MUST take precautions to prevent leakage and abuse of its credentials. Client authentication allows an authorization server to ensure it is interacting with a certain client (identified by its client_id) in an OAuth flow. The authorization server might make policy decisions about things such as whether to prompt the user for consent on every authorization or only the first time, based on the confidence that the authorization server is actually communicating with the legitimate client. Whether and how an authorization server validates the identity of a client or the party providing/operating this client is out of scope for this specification. Authorization servers SHOULD consider the level of confidence in a client's identity before allowing that client to perform actions that carry elevated risk, such as:

accessing sensitive resources or performing sensitive operations,
using a non-interactive grant type such as the client credentials grant, or
skipping the user consent prompt on subsequent authorizations.

There is no requirement that an authorization server support a particular client type. A single client_id SHOULD NOT be treated as more than one type of client. This specification has been designed around the following client profiles:

"web application":: A web application is a client running on a web server. Resource owners access the client via an HTML user interface rendered in a user agent on the device used by the resource owner. The client credentials as well as any access tokens issued to the client are stored on the web server and are not exposed to or accessible by the resource owner.
"browser-based application":: A browser-based application is a client in which the client code is downloaded from a web server and executes within a user agent (e.g., a web browser) on the device used by the resource owner. Protocol data and credentials are easily accessible (and often visible) to the resource owner. If such applications wish to use client credentials, it is recommended to use the backend for frontend pattern (). Since such applications reside within the user agent, they can make seamless use of the user agent capabilities when requesting authorization.
"native application":: A native application is a client installed and executed on the device used by the resource owner. Protocol data and credentials are accessible to the resource owner. It is assumed that any client authentication credentials included in the application can be extracted. Dynamically issued access tokens and refresh tokens can receive an acceptable level of protection. On some platforms, these credentials are protected from other applications residing on the same device. If such applications wish to use client credentials, it is recommended to use the backend for frontend pattern or to issue the credentials at runtime using Dynamic Client Registration .

Client Identifier Every client is identified in the context of an authorization server by a client identifier -- a unique string representing the registration information provided by the client. While the authorization server typically issues the client identifier itself, it may also serve clients whose client identifier was created by a party other than the authorization server. The client identifier is not a secret; it is exposed to the resource owner and MUST NOT be used alone for client authentication. The client identifier is unique in the context of an authorization server. The client identifier is an opaque string whose length is left undefined by this specification, as described in . If the authorization server supports clients with client identifiers issued by parties other than the authorization server, the authorization server SHOULD take precautions to avoid clients impersonating resource owners as described in .

Client Redirection Endpoint The client redirection endpoint (also referred to as the "redirect endpoint") is the URI of the client that the authorization server redirects the user agent back to after completing its interaction with the resource owner. The authorization server redirects the user agent to one of the client's redirection endpoints previously established with the authorization server during the client registration process. The redirect URI MUST be an absolute URI as defined by . The redirect URI MAY include a query string component (), which MUST be retained when adding additional query parameters. The query string component MUST NOT include any parameters defined for use in the authorization response. The redirect URI MUST NOT include a fragment component.

Registration Requirements Authorization servers MUST require clients to register their complete redirect URI (including the path component). Authorization servers MUST reject authorization requests that specify a redirect URI that doesn't exactly match one that was registered, with an exception for loopback interface redirect URIs, where an exact match is required except for the port URI component; see for details. The authorization server MAY allow the client to register multiple redirect URIs. Registration may happen out of band, such as a manual step of configuring the client information at the authorization server, or may happen at runtime, such as in the initial POST in Pushed Authorization Requests . For private-use URI scheme-based redirect URIs, authorization servers SHOULD enforce the requirement in that clients use schemes that are based on reverse domain names. At a minimum, any private-use URI scheme that doesn't contain a period character (.) SHOULD be rejected. In addition to providing collision resistance, this requirement can help to prove ownership in the event of a dispute where two apps claim the same private-use URI scheme (where one app is acting maliciously). For example, if two apps claim com.example.app, the owner of example.com could petition the app store operator to remove the counterfeit app. Such a petition is harder to prove if a generic URI scheme is used. Clients MUST NOT expose URLs that forward the user's browser to arbitrary URIs obtained from a query parameter ("open redirector"), as described in . Open redirectors can enable exfiltration of authorization codes and access tokens. The client MAY use the state request parameter to achieve per-request customization if needed rather than varying the redirect URI per request. Without requiring registration of redirect URIs, attackers can use the authorization endpoint as an open redirector as described in .

Multiple Redirect URIs If multiple redirect URIs have been registered for a client, the client MUST include a redirect URI with the authorization request using the redirect_uri request parameter (). If only a single redirect URI has been registered for a client, the redirect_uri request parameter is optional.

Preventing CSRF Attacks Clients MUST prevent Cross-Site Request Forgery (CSRF) attacks. In this context, CSRF refers to requests to the redirection endpoint that do not originate at the authorization server, but at a malicious third party (see for details). Clients that have ensured that the authorization server supports the code_challenge parameter MAY rely on the CSRF protection provided by that mechanism. In OpenID Connect flows, validating the nonce parameter provides CSRF protection. Otherwise, one-time-use CSRF tokens carried in the state parameter that are securely bound to the user agent MUST be used for CSRF protection (see ).

Preventing Mix-Up Attacks When an OAuth client can only interact with one authorization server, a mix-up defense is not required. In scenarios where an OAuth client interacts with two or more authorization servers, however, clients MUST prevent mix-up attacks. In order to prevent mix-up attacks, clients MUST only process redirect responses from the issuer to which they sent the respective request, and from the same user agent in which the authorization request was initiated. See for a detailed description of two different defenses against mix-up attacks.

Invalid Endpoint If an authorization request fails validation due to a missing, invalid, or mismatching redirect URI, the authorization server SHOULD inform the resource owner of the error and MUST NOT automatically redirect the user agent to the invalid redirect URI.

Endpoint Content The redirection request to the client's endpoint typically results in an HTML document response, processed by the user agent. If the HTML response is served directly as the result of the redirection request, any script included in the HTML document will execute with full access to the redirect URI and the artifacts (e.g., authorization code) it contains. Additionally, the request URL containing the authorization code may be sent in the Referer header field () to any embedded images, stylesheets, and other elements loaded in the page. The client SHOULD NOT include any third-party scripts (e.g., third-party analytics, social plug-ins, ad networks) in the redirect URI endpoint response. Instead, it SHOULD extract the artifacts from the URI and redirect the user agent again to another endpoint without exposing the artifacts (in the URI or elsewhere). If third-party scripts are included, the client MUST ensure that its own scripts (used to extract and remove the credentials from the URI) will execute first.

Client Authentication The authorization server MUST only rely on client authentication if the process of issuance/registration and distribution of the underlying credentials ensures their confidentiality. For confidential clients, the authorization server MAY accept any form of client authentication meeting its security requirements (e.g., client secret, public/private key pair). It is RECOMMENDED to use asymmetric (public-key-based) methods for client authentication, such as mTLS or signed JWTs ("Private Key JWT") in accordance with , , and their update (defined in as the client authentication method private_key_jwt). When such methods for client authentication are used, authorization servers do not need to store sensitive symmetric keys, which makes these methods more robust against a number of attacks and enables clients to manage their own keys and key rotation. When using JWT-based client authentication, clients and authorization servers MUST follow the updated guidance around aud values in . When client authentication is not possible, the authorization server SHOULD employ other means to validate the client's identity -- for example, by requiring the registration of the client redirect URI or enlisting the resource owner to confirm identity. A valid redirect URI is not sufficient to verify the client's identity when asking for resource owner authorization but can be used to prevent delivering credentials to a counterfeit client after obtaining resource owner authorization. The client MUST NOT use more than one authentication method in each request to prevent a conflict over which authentication mechanism is authoritative for the request. The authorization server MUST consider the security implications of interacting with unauthenticated clients and take measures to limit the potential exposure of tokens issued to such clients (e.g., by limiting the lifetime of refresh tokens). The privileges an authorization server associates with a certain client identity MUST depend on the assessment of the overall process for client identification and client credential lifecycle management. See for additional details.

Client Secret To support confidential clients in possession of a client secret, the authorization server MUST support the client including the client credentials in the request content using the following parameters:

"client_id":: REQUIRED. The client identifier issued to the client during the registration process described in .
"client_secret":: REQUIRED. The client secret.

The parameters can only be transmitted in the request content and MUST NOT be included in the target URI. This is also known as client_secret_post as defined in . For example, a request to refresh an access token () using the content parameters: The authorization server MAY support the HTTP Basic authentication scheme for authenticating clients that were issued a client secret. When using the HTTP Basic authentication scheme as defined in to authenticate with the authorization server, the client identifier is encoded using the application/x-www-form-urlencoded encoding algorithm per , and the encoded value is used as the username; the client secret is encoded using the same algorithm and used as the password. This is also known as client_secret_basic as defined in . For example, the same request to refresh an access token using the HTTP Basic authentication scheme: Note: This method of initially form-encoding the client identifier and secret, and then using the encoded values as the HTTP Basic authentication username and password, has led to many interoperability problems in the past. Some implementations have missed the encoding step, or decided to only encode certain characters, or ignored the encoding requirement when validating the credentials, leading to clients having to special-case how they present the credentials to individual authorization servers. Including the credentials in the request content avoids the encoding issues and leads to more interoperable implementations. Since the client secret authentication method involves a password, the authorization server MUST protect any endpoint utilizing it against brute-force attacks.

Other Authentication Methods The authorization server MAY support any suitable authentication scheme matching its security requirements. When using other authentication methods, the authorization server MUST define a mapping between the client identifier (registration record) and the authentication scheme. Some additional authentication methods such as mTLS and Private Key JWT (, ) are defined in the "OAuth Token Endpoint Authentication Methods" registry, and may be useful as generic client authentication methods beyond the specific use of protecting the token endpoint.

Unregistered Clients This specification does not require that clients be registered with the authorization server. However, the use of unregistered clients is beyond the scope of this specification and requires additional security analysis and review of its interoperability impact.

Protocol Endpoints The authorization process utilizes two authorization server endpoints (HTTP resources):

Authorization endpoint - used by the client to obtain authorization from the resource owner via user agent redirection.
Token endpoint - used by the client to exchange an authorization grant for an access token, typically with client authentication.

As well as one client endpoint:

Redirection endpoint - used by the authorization server to return responses containing authorization credentials to the client via the resource owner's user agent.

Not every authorization grant type utilizes both endpoints. Extension grant types MAY define additional endpoints as needed.

Authorization Endpoint The authorization endpoint is used to interact with the resource owner and obtain an authorization grant. The authorization server MUST first authenticate the resource owner. The way in which the authorization server authenticates the resource owner (e.g., username and password login, passkey, federated login, or by using an established session) is beyond the scope of this specification. The means through which the client obtains the URL of the authorization endpoint are beyond the scope of this specification, but the URL is typically provided in the service documentation, or in the authorization server's metadata document . The authorization endpoint URL MUST NOT include a fragment component, and MAY include a query string component (), which MUST be retained when adding additional query parameters. The query string component MUST NOT include any parameters defined for use in the authorization request. The authorization server MUST support the use of the HTTP GET method () for the authorization endpoint and MAY support the POST method () as well. When using GET, the request parameters are serialized using . When using POST, the request parameters are serialized using . The authorization server MUST ignore unrecognized request parameters sent to the authorization endpoint. Request and response parameters defined by this specification MUST NOT be included more than once. This requirement also applies to parameters defined by extensions unless the extension explicitly defines otherwise for a specific parameter. Parameters sent without a value MUST be treated as if they were omitted from the request. An authorization server that redirects a request potentially containing user credentials MUST avoid forwarding these user credentials accidentally (see for details). Cross-Origin Resource Sharing MUST NOT be supported at the authorization endpoint, as the client does not access this endpoint directly; instead, the client redirects the user agent to it. Grant types define the required parameters at the authorization endpoint. This specification defines the "Authorization Code Grant" (), including the base list of parameters to include in the request. Extensions such as Pushed Authorization Requests () define a different set of parameters to use in the request to the authorization endpoint.

Token Endpoint The token endpoint is used by the client to obtain an access token using a grant such as those described in and . The means through which the client obtains the URL of the token endpoint are beyond the scope of this specification, but the URL is typically provided in the service documentation and configured during development of the client, or provided in the authorization server's metadata document and fetched programmatically at runtime. The token endpoint URL MUST NOT include a fragment component, and MAY include a query string component (). The client MUST use the HTTP POST method when making requests to the token endpoint. The authorization server MUST ignore unrecognized request parameters sent to the token endpoint. Parameters sent without a value MUST be treated as if they were omitted from the request. Request and response parameters defined by this specification MUST NOT be included more than once. This requirement also applies to parameters defined by extensions unless the extension explicitly defines otherwise for a specific parameter. Authorization servers that support browser-based applications (for example, applications running exclusively in client-side JavaScript without access to a supporting backend server) MUST ensure the token endpoint supports the necessary CORS header fields to allow the responses to be visible to the application. If the authorization server provides additional endpoints to the application, such as metadata URLs, dynamic client registration, revocation, introspection, discovery, or user info endpoints, these endpoints may also be accessed by the browser-based application and MUST also send the CORS header fields to allow access. Note that CORS header fields are not needed in the case where the browser-based application shares an origin with the authorization server. See and for further details.

Client Authentication Confidential clients MUST authenticate with the authorization server as described in when making requests to the token endpoint. Client authentication is used for:

Enforcing the binding of refresh tokens and authorization codes to the client to which they were issued. Client authentication adds an additional layer of security when an authorization code is transmitted to the redirection endpoint over an insecure channel.
Recovering from a compromised client by disabling the client or changing its credentials, thus preventing an attacker from abusing stolen refresh tokens. Changing a single set of client credentials is significantly faster than revoking an entire set of refresh tokens.
Implementing authentication management best practices, which require periodic credential rotation. Rotation of an entire set of refresh tokens can be challenging, while rotation of a single set of client credentials is significantly easier.

Token Endpoint Request The client makes a request to the token endpoint by sending the following parameters using the form-encoded serialization format per with a character encoding of UTF-8 in the HTTP request content:

"grant_type":: REQUIRED. Identifier of the grant type the client uses with the particular token request. This specification defines the values authorization_code, refresh_token, and client_credentials. The grant type determines the further parameters required or supported by the token request. The details of those grant types are defined below.
"client_id":: OPTIONAL. The client identifier is needed when a form of client authentication that relies on the parameter is used, or the grant_type requires identification of public clients.

Confidential clients MUST authenticate with the authorization server as described in . For example, the client makes the following HTTPS request: The authorization server MUST:

require client authentication for confidential clients (or clients with other authentication requirements), and
authenticate the client if client authentication is included.

Further grant-type-specific processing rules apply and are specified with the respective grant type.

Token Endpoint Response If the access token request is valid and authorized, the authorization server issues an access token and, optionally, a refresh token. If client authentication fails or is invalid, the authorization server returns an error response as described in . The authorization server issues an access token and, optionally, a refresh token by creating an HTTP response according to , using the application/json media type as defined by , with the following parameters and a 200 (OK) status code:

"access_token":: REQUIRED. The access token issued by the authorization server.
"token_type":: REQUIRED. The type of the access token issued as described in . The value is case insensitive.
"expires_in":: RECOMMENDED. A JSON number that represents the lifetime in seconds of the access token. For example, the value 3600 denotes that the access token will expire one hour from the time the response was generated. If omitted, the authorization server SHOULD provide the lifetime via other means or document the default value. Note that the authorization server may prematurely expire an access token, and clients MUST NOT expect an access token to be valid for the provided lifetime.
"scope":: RECOMMENDED, if identical to the scope requested by the client; otherwise, REQUIRED. The scope of the access token as described by .
"refresh_token":: OPTIONAL. The refresh token, which can be used to obtain new access tokens based on the grant passed in the corresponding token request.

Authorization servers SHOULD determine, based on a risk assessment and their own policies, whether to issue refresh tokens to a certain client. For example, an authorization server might issue refresh tokens only to clients that are registered to receive them, only when the client requests a particular scope (such as the offline_access scope defined in ), or depending on whether the client is confidential or public, and might tie the lifetime of the refresh token to the resource owner's session at the authorization server, as recommended for browser-based applications in . If the authorization server decides not to issue refresh tokens, the client MAY obtain new access tokens by starting the OAuth flow over, for example, by initiating a new authorization code request. In such a case, the authorization server may utilize cookies and persistent grants to optimize the user experience. If refresh tokens are issued, those refresh tokens MUST be bound to the scope and resource servers as consented by the resource owner. This is to prevent privilege escalation by the legitimate client and to reduce the impact of refresh token leakage. The parameters are serialized into a JavaScript Object Notation (JSON) structure as described in . The authorization server MUST include the Cache-Control response header field () with a value of no-store in any response containing tokens, credentials, or other sensitive information. For example: The client MUST ignore unrecognized value names in the response. The length of tokens and other values received from the authorization server is left undefined, as described in .

Token Endpoint Error Response The authorization server responds with a 400 (Bad Request) status code (unless specified otherwise) and includes the following parameters with the response:

"error":

REQUIRED. A single ASCII error code from the following:

"invalid_request":: The request is missing a required parameter, includes an unsupported parameter value (other than grant type), repeats a parameter, includes multiple credentials, utilizes more than one mechanism for authenticating the client, contains a code_verifier although no code_challenge was sent in the authorization request, or is otherwise malformed.
"invalid_client":: Client authentication failed (e.g., unknown client, no client authentication included, or unsupported authentication method). The authorization server MAY return a 401 (Unauthorized) status code to indicate which HTTP authentication schemes are supported. If the client attempted to authenticate via the Authorization request header field (), the authorization server MUST respond with a 401 (Unauthorized) status code and include the WWW-Authenticate response header field () matching the authentication scheme used by the client. Client authentication methods that do not use an HTTP authentication scheme have no corresponding challenge in the WWW-Authenticate header field.
"invalid_grant":: The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirect URI used in the authorization request, or was issued to another client.
"unauthorized_client":: The authenticated client is not authorized to use this authorization grant type.
"unsupported_grant_type":: The authorization grant type is not supported by the authorization server.
"invalid_scope":: The requested scope is invalid, unknown, malformed, or exceeds the scope granted by the resource owner.

Values for the error parameter MUST NOT include characters outside the set %x20-21 / %x23-5B / %x5D-7E.

"error_description":

OPTIONAL. Human-readable ASCII text providing additional information, used to assist the client developer in understanding the error that occurred. Values for the error_description parameter MUST NOT include characters outside the set %x20-21 / %x23-5B / %x5D-7E.

"error_uri":

OPTIONAL. A URI identifying a human-readable web page with information about the error, used to provide the client developer with additional information about the error. Values for the error_uri parameter MUST conform to the URI-reference syntax and thus MUST NOT include characters outside the set %x21 / %x23-5B / %x5D-7E.

The parameters are included in the content of the HTTP response using the application/json media type as defined in . For example:

Grant Types To request an access token, the client obtains authorization from the resource owner. This specification defines the following authorization grant types:

authorization code
client credentials
refresh token

It also provides an extension mechanism for defining additional grant types.

Authorization Code Grant The authorization code grant type is used to obtain both access tokens and refresh tokens. The grant type uses the additional authorization endpoint to let the authorization server interact with the resource owner in order to get consent for resource access. Since this is a redirect-based flow, the client must be capable of initiating the flow with the resource owner's user agent (typically a web browser) and capable of receiving incoming requests (via redirection) from the authorization server.

Authorization Code Flow | | | | | | | | | | '---------(2)-- User authenticates --->| | | | User- | | Authorization | | | Agent | | Server | | | | | | | | .--------(3)-- Authorization Code ---<| | +-|----|---+ +---------------+ | | ^ v | | | | ^ v | | +---------+ | | | |>---(4)-- Authorization Code ---------' | | Client | & Redirect URI | | | | | |<---(5)----- Access Token -------------------' +---------+ (w/ Optional Refresh Token) ]]> The flow illustrated in includes the following steps: (1) The client initiates the flow by directing the resource owner's user agent to the authorization endpoint. The client includes its client identifier, code challenge (derived from a generated code verifier), optional requested scope, optional local state, and a redirect URI to which the authorization server will send the user agent back once access is granted (or denied). (2) The authorization server authenticates the resource owner (via the user agent) and establishes whether the resource owner grants or denies the client's access request. (3) Assuming the resource owner grants access, the authorization server redirects the user agent back to the client using the redirect URI provided earlier (in the request or during client registration). The redirect URI includes an authorization code and any local state provided by the client earlier. (4) The client requests an access token from the authorization server's token endpoint by including the authorization code received in the previous step, and including its code verifier. When making the request, the client authenticates with the authorization server if it can. The client includes the redirect URI used to obtain the authorization code for verification. (5) The authorization server authenticates the client when possible, validates the authorization code, validates the code verifier, and ensures that the redirect URI received matches the URI used to redirect the user agent to the client in step (3). If valid, the authorization server responds with an access token and, optionally, a refresh token.

Authorization Request To begin the authorization request, the client builds the authorization request URL by adding parameters to the authorization server's authorization endpoint URL. The client will eventually redirect the user agent to this URL to initiate the request. Clients use a unique secret, called the "code verifier", per authorization request to protect against authorization code injection and CSRF attacks. The client first generates the code verifier, then derives the "code challenge" to include in the authorization request. The client uses the code verifier when exchanging the authorization code at the token endpoint to prove that the client using the authorization code is the same client that requested it. The client constructs the request URL by adding the following parameters to the query component of the authorization endpoint URL as described by :

"response_type":: REQUIRED. The authorization endpoint supports different sets of request and response parameters. The client determines the type of flow by using a certain response_type value. This specification defines the value code, which must be used to signal that the client wants to use the authorization code flow.

Extension response types MAY contain a space-delimited (%x20) set of values, where the order of values does not matter (e.g., response type a b is the same as b a). The meaning of such composite response types is defined by their respective specifications. Some extension response types are defined by . If an authorization request is missing the response_type parameter, or if the response type is not understood, the authorization server MUST return an error response as described in .

"client_id":: REQUIRED. The client identifier as described in .
"code_challenge":: REQUIRED unless the specific requirements of are met. The code challenge derived from the code verifier.
"code_challenge_method":: REQUIRED. The code challenge transformation method: either S256 or a value defined by a future extension.
"redirect_uri":: OPTIONAL if only one redirect URI is registered for this client. REQUIRED if multiple redirect URIs are registered for this client. See .
"scope":: OPTIONAL. The scope of the access request as described by .
"state":: OPTIONAL. An opaque value used by the client to maintain state between the request and callback. The authorization server includes this value when redirecting the user agent back to the client. This value is carried in the query component of the authorization request URL and again in the redirect back to the client, so its length is bounded in practice by the URL and HTTP header field lengths accepted by the authorization server, the user agent, and the client; see .

The code_verifier is a unique, high-entropy, cryptographically random string generated for each authorization request, using the unreserved characters [A-Z] / [a-z] / [0-9] / "-" / "." / "_" / "~", with a minimum length of 43 characters and a maximum length of 128 characters. The client stores the code_verifier temporarily and calculates the code_challenge, which it uses in the authorization request. The ABNF for code_verifier is as follows. Clients MUST use code challenge methods that do not expose the code_verifier in the authorization request. Otherwise, attackers that can read the authorization request (cf. Attacker A4 in ) can break the security provided by this mechanism. Currently, S256 is the only such method. NOTE: The code verifier SHOULD have enough entropy to make it impractical to guess the value. It is RECOMMENDED that the output of a suitable random number generator be used to create a 32-octet sequence. The octet sequence is then base64url-encoded to produce a 43-octet URL-safe string to use as the code verifier. The client then creates a code_challenge derived from the code verifier by transforming the code verifier with a valid transformation method: This specification defines only the S256 transformation. Future extensions may define additional transformation methods. The ABNF for code_challenge is as follows. The properties code_challenge and code_verifier are adopted from the OAuth 2.0 extension known as "Proof Key for Code Exchange", or PKCE , where this technique was originally developed. The plain transformation method defined in is removed and explicitly prohibited in this specification. See for additional details. Authorization servers MUST support the code_challenge and code_verifier parameters. Clients MUST use code_challenge and code_verifier, and authorization servers MUST enforce their use except under the conditions described in . Even in this case, using and enforcing code_challenge and code_verifier as described above is still RECOMMENDED. The state and scope parameters SHOULD NOT include sensitive client or resource owner information in cleartext, as they can be transmitted over insecure channels or stored insecurely. The client directs the resource owner to the constructed URI using an HTTP redirection, or by other means available to it via the user agent. For example, the client directs the user agent to make the following HTTPS request: The authorization server validates the request to ensure that all required parameters are present and valid. In particular, the authorization server MUST validate the redirect_uri in the request if present, ensuring that it matches one of the registered redirect URIs previously established during client registration (). When comparing the two URIs the authorization server MUST ensure that the two URIs are equal using simple string comparison as defined in , i.e., a case-sensitive, character-by-character comparison with no normalization applied. The only exception is loopback interface redirect URIs used by native apps: in this case, the authorization server MUST allow variable port numbers as described in . If the request is valid, the authorization server authenticates the resource owner and obtains an authorization decision (by asking the resource owner or by establishing approval via other means). When a decision is established, the authorization server directs the user agent to the provided client redirect URI using an HTTP redirection response, or by other means available to it via the user agent.

Authorization Response If the resource owner grants the access request, the authorization server issues an authorization code and delivers it to the client by adding the following parameters to the query component of the redirect URI using the query string serialization described by , unless specified otherwise by an extension:

"code":: REQUIRED. The authorization code is generated by the authorization server and opaque to the client. The authorization code MUST expire shortly after it is issued to mitigate the risk of leaks. A maximum authorization code lifetime of 10 minutes is RECOMMENDED. The authorization code is bound to the client identifier, code challenge, and redirect URI.
"state":: REQUIRED if the state parameter was present in the client authorization request. The exact value received from the client.
"iss":: REQUIRED. The issuer identifier of the authorization server, which the client can use to prevent mix-up attacks, if the client interacts with more than one authorization server. See and for additional details on how the client can use it to prevent mix-up attacks.

For example, the authorization server redirects the user agent by sending the following HTTP response: The client MUST ignore unrecognized response parameters. The length of the authorization code string is left undefined by this specification, as described in . The authorization server MUST associate the code_challenge and code_challenge_method values with the issued authorization code so the code challenge can be verified later. The exact method that the server uses to associate the code_challenge with the issued code is out of scope for this specification. The code challenge could be stored on the server and associated with the code there. The code_challenge and code_challenge_method values may be stored in encrypted form in the code itself, but the server MUST NOT include the code_challenge value in a response parameter in a form that entities other than the AS can extract. Clients MUST prevent injection (replay) of authorization codes into the authorization response by attackers. Using code_challenge and code_verifier prevents injection of authorization codes since the authorization server will reject a token request with a mismatched code_verifier. See for more details.

Authorization Error Response If the request fails due to a missing, invalid, or mismatching redirect URI, or if the client identifier is missing or invalid, the authorization server MUST NOT redirect the user agent to the invalid redirect URI and SHOULD inform the resource owner of the error, for example, by displaying a message to the user in their browser. When returning an error response directly to the user agent, the authorization server SHOULD use the 400 (Bad Request) status code. The 401 (Unauthorized) status code used for client authentication errors at the token endpoint does not apply to authorization endpoint request errors. The authorization server MUST validate the client identifier and redirect URI before redirecting an error response to the client. Once both have been validated, the authorization server redirects request errors using the error codes defined below. An authorization server MUST reject requests without a code_challenge from public clients, and MUST reject such requests from other clients unless there is reasonable assurance that the client mitigates authorization code injection in other ways. See for details. If the server does not support the requested code_challenge_method transformation, the authorization endpoint MUST return the authorization error response with the error value set to invalid_request. The error_description or the resource referenced by error_uri SHOULD explain the nature of the error (e.g., that the transform algorithm is not supported). If the resource owner denies the access request or if the request fails after the client identifier and redirect URI have been validated, the authorization server informs the client by redirecting the user agent to the redirect URI and adding the following parameters to the query component of the redirect URI as described by :

"error":

REQUIRED. A single ASCII error code from the following:

"invalid_request":: The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed.
"unauthorized_client":: The client is not authorized to request an authorization code using this method.
"access_denied":: The resource owner or authorization server denied the request.
"unsupported_response_type":: The authorization server does not support obtaining an authorization code using this method.
"invalid_scope":: The requested scope is invalid, unknown, or malformed.
"server_error":: The authorization server encountered an unexpected condition that prevented it from fulfilling the request. (This error code is needed because a 500 (Internal Server Error) status code cannot be returned to the client via an HTTP redirect.)
"temporarily_unavailable":: The authorization server is currently unable to handle the request due to a temporary overloading or maintenance of the server. (This error code is needed because a 503 (Service Unavailable) status code cannot be returned to the client via an HTTP redirect.)

Values for the error parameter MUST NOT include characters outside the set %x20-21 / %x23-5B / %x5D-7E.

"error_description":

"error_uri":

"state":

REQUIRED if a state parameter was present in the client authorization request. The exact value received from the client.

"iss":

REQUIRED. The issuer identifier of the authorization server. See above for details.

For example, the authorization server indicates that the request was denied by redirecting the user agent with the following HTTP response:

Token Endpoint Extension The authorization code grant type is identified at the token endpoint with the grant_type value of authorization_code. If this value is set, the following additional token request parameters beyond are supported:

"code":: REQUIRED. The authorization code received from the authorization server.
"code_verifier":: REQUIRED, if the code_challenge parameter was included in the authorization request. MUST NOT be used otherwise. The original code verifier string.
"client_id":: REQUIRED, if the client is not authenticating with the authorization server as described in .

The authorization server MUST return an access token only once for a given authorization code. If a second valid token request is made with the same authorization code as a previously successful token request, the authorization server MUST deny the request and SHOULD revoke (when possible) all access tokens and refresh tokens previously issued based on that authorization code. See for further details. For example, the client makes the following HTTPS request: In addition to the processing rules in , the authorization server MUST:

ensure that the authorization code was issued to the authenticated confidential client or, if the client is public, ensure that the code was issued to the client_id in the request,
verify that the authorization code is valid,
verify that the code_verifier parameter is present if and only if a code_challenge parameter was present in the authorization request,
if a code_verifier is present, verify the code_verifier by calculating the code challenge from the received code_verifier and comparing it with the previously associated code_challenge, after first transforming it according to the code_challenge_method method specified by the client, and
reject the token request if there was no code_challenge in the authorization request associated with the authorization code in the token request.

See for details on backward compatibility with OAuth 2.0 clients regarding the redirect_uri parameter in the token request.

Client Credentials Grant The client can request an access token using only its client credentials (or other supported means of authentication) when the client is requesting access to the protected resources under its control, or those of another resource owner that have been previously arranged with the authorization server (the method of which is beyond the scope of this specification). The client credentials grant type MUST only be used by confidential clients.

Client Credentials Grant --(1)- Client Authentication --->| Authorization | | Client | | Server | | |<--(2)---- Access Token ---------<| | | | | | +---------+ +---------------+ ]]> The use of the client credentials grant illustrated in includes the following steps: (1) The client authenticates with the authorization server and requests an access token from the token endpoint. (2) The authorization server authenticates the client, and if valid, issues an access token.

Token Endpoint Extension The client credentials grant type is identified at the token endpoint with the grant_type value of client_credentials. If this value is set, the following additional token request parameters beyond are supported:

"scope":: OPTIONAL. The scope of the access request as described by .

For example, the client makes the following HTTP request using transport-layer security: The authorization server MUST authenticate the client.

Refresh Token Grant The refresh token is a credential issued by the authorization server to a client, which can be used to obtain new (fresh) access tokens based on an existing grant. The client uses this option either because the previous access token has expired or the client previously obtained an access token with a scope narrower than that approved by the respective grant and later requires an access token with a different scope under the same grant. Refresh tokens MUST be kept confidential in transit and storage, and shared only between the authorization server and the client to which the refresh tokens were issued. The authorization server MUST maintain the binding between a refresh token and the client to which it was issued. The authorization server MUST verify the binding between the refresh token and the client identity whenever the client identity can be authenticated. When client authentication is not possible, the authorization server SHOULD issue sender-constrained refresh tokens or use refresh token rotation as described in . The authorization server MUST ensure that refresh tokens cannot be generated, modified, or guessed to produce valid refresh tokens by unauthorized parties.

Token Endpoint Extension The refresh token grant type is identified at the token endpoint with the grant_type value of refresh_token. If this value is set, the following additional parameters beyond are supported:

"refresh_token":: REQUIRED. The refresh token issued to the client.
"scope":: OPTIONAL. The scope of the access request as described by . The requested scope MUST NOT include any scope not originally granted by the resource owner and, if omitted, is treated as equal to the scope originally granted by the resource owner.

Because refresh tokens are typically long-lasting credentials used to request additional access tokens, the refresh token is bound to the client to which it was issued. Confidential clients MUST authenticate with the authorization server as described in . For example, the client makes the following HTTP request using transport-layer security: In addition to the processing rules in , the authorization server MUST:

if client authentication is included in the request, ensure that the refresh token was issued to the authenticated client or, if a client_id is included in the request, ensure that the refresh token was issued to the matching client,
validate that the grant corresponding to this refresh token is still active, and
validate the refresh token.

If the authorization associated with the grant has been reduced since the refresh token was issued (e.g., the resource owner revoked some scopes), the authorization server MAY issue an access token with the reduced scope, in which case it MUST include the scope response parameter as described in . Authorization servers MUST utilize one of these methods to detect refresh token replay by malicious actors for public clients:

Sender-constrained refresh tokens: the authorization server cryptographically binds the refresh token to a certain client instance, e.g., by utilizing DPoP or mTLS .
Refresh token rotation: the authorization server issues a new refresh token with every access token refresh response. The previous refresh token is invalidated, but information about the relationship is retained by the authorization server. If a refresh token is compromised and subsequently used by both the attacker and the legitimate client, one of them will present an invalidated refresh token, which will inform the authorization server of the breach. The authorization server cannot determine which party submitted the invalid refresh token, but it will revoke the active refresh token as well as the access authorization grant associated with it. This stops the attack at the cost of forcing the legitimate client to obtain a fresh authorization grant.

Implementation note: the grant to which a refresh token belongs may be encoded into the refresh token itself. This can enable an authorization server to efficiently determine the grant to which a refresh token belongs and, by extension, all refresh tokens that need to be revoked. Authorization servers MUST ensure the integrity of the refresh token value in this case, for example, by using signatures.

Refresh Token Response If valid and authorized, the authorization server issues an access token as described in . The authorization server MAY issue a new refresh token, in which case the client MUST discard the old refresh token and replace it with the new refresh token.

Refresh Token Recommendations The authorization server MAY revoke the old refresh token after issuing a new refresh token to the client. If a new refresh token is issued, the refresh token scope MUST be identical to that of the refresh token included by the client in the request, unless the grant has been reduced as described in . Authorization servers MAY revoke refresh tokens automatically in case of a security event, such as:

password change
logout at the authorization server

Refresh tokens SHOULD expire if the client has been inactive for some time, i.e., the refresh token has not been used to obtain new access tokens for some time. The expiration time is at the discretion of the authorization server. It might be a global value or determined based on the client policy or the grant associated with the refresh token (and its sensitivity). When refresh token rotation is used, a failure to deliver the refresh token response (e.g., due to a network error) can leave the client holding only an invalidated refresh token, forcing a new authorization flow. Authorization servers that wish to avoid this failure mode can use sender-constrained refresh tokens instead of rotation.

Extension Grants The client uses an extension grant type by specifying the grant type using an absolute URI (defined by the authorization server) as the value of the grant_type parameter of the token endpoint, and by adding any additional parameters necessary. For example, to request an access token using the Device Authorization Grant as defined by after the user has authorized the client on a separate device, the client makes the following HTTPS request: If the access token request is valid and authorized, the authorization server issues an access token and, optionally, a refresh token as described in . If the request failed client authentication or is invalid, the authorization server returns an error response as described in .

Resource Requests The client accesses protected resources by presenting an access token to the resource server. The resource server MUST validate the access token and ensure that it has not expired and that its scope covers the requested resource. The methods used by the resource server to validate the access token are beyond the scope of this specification, but generally involve an interaction or coordination between the resource server and the authorization server. For example, when the resource server and authorization server are colocated or are part of the same system, they may share a database or other storage; when the two components are operated independently, they may use Token Introspection or a structured access token format such as a JWT .

Bearer Token Requests This section defines two methods of sending bearer tokens in resource requests to resource servers. Clients MUST use one of the two methods defined below, and MUST NOT use more than one method to transmit the token in each request. In particular, clients MUST NOT send the access token in a URI query parameter, and resource servers MUST ignore access tokens in a URI query parameter.

Authorization Request Header Field When sending the access token in the Authorization request header field defined in , the client uses the Bearer scheme to transmit the access token. For example: The syntax of the Authorization header field for this scheme follows the usage of the Basic scheme defined in . As with Basic, the credentials use the token68 syntax () rather than the auth-param syntax, in order to reflect existing deployments; this syntax is compatible with the general authentication framework in . The syntax for Bearer credentials is as follows: Clients SHOULD make authenticated requests with a bearer token using the Authorization request header field with the Bearer HTTP authorization scheme. Resource servers MUST support this method. As described in , the string bearer is case insensitive. This means all of the following are valid uses of the Authorization header field:

Authorization: Bearer mF_9.B5f-4.1JqM
Authorization: bearer mF_9.B5f-4.1JqM
Authorization: BEARER mF_9.B5f-4.1JqM
Authorization: bEaReR mF_9.B5f-4.1JqM

Form-Encoded Content Parameter When sending the access token in the HTTP request content, the client adds the access token to the request content using the access_token parameter. The client MUST NOT use this method unless all of the following conditions are met:

The HTTP request includes the Content-Type header field () set to application/x-www-form-urlencoded.
The content follows the encoding requirements of the application/x-www-form-urlencoded media type as defined by the URL Living Standard .
The HTTP request content is single-part.
The content to be encoded in the request MUST consist entirely of ASCII characters.
The HTTP request method is one for which the content has defined semantics. In particular, this means that the GET method MUST NOT be used.

The content MAY include other request-specific parameters, in which case the access_token parameter MUST be properly separated from the request-specific parameters using & character(s) (ASCII code 38). For example, the client makes the following HTTP request using transport-layer security: The application/x-www-form-urlencoded method SHOULD NOT be used except in application contexts where participating clients do not have access to the Authorization request header field. Resource servers MAY support this method.

Access Token Validation After receiving the access token, the resource server MUST check that the access token has not expired, is authorized to access the requested resource, was issued with the appropriate scope, and meets other policy requirements of the resource server to access the protected resource. Access tokens generally fall into two categories: reference tokens or self-encoded tokens. Reference tokens can be validated by querying the authorization server or looking up the token in a token database, whereas self-encoded tokens contain the authorization information in an encrypted and/or signed string that can be extracted by the resource server. A standardized method to query the authorization server to check the validity of an access token is defined in Token Introspection . A standardized method of encoding information in a token string is defined in the JWT Profile for Access Tokens . See for additional considerations around creating and validating access tokens.

Error Response If a resource access request fails, the resource server SHOULD inform the client of the error. The details of the error response are determined by the particular token type, such as the description of bearer tokens in .

The WWW-Authenticate Response Header Field If the protected resource request does not include authentication credentials or does not contain an access token that enables access to the protected resource, the resource server MUST include the WWW-Authenticate response header field; it MAY include it in response to other conditions as well. The WWW-Authenticate header field uses the framework defined in . All challenges for this token type MUST use the auth-scheme value Bearer. This scheme MAY be followed by one or more auth-param values. The auth-param attributes used or defined by this specification for this token type are as follows. Other auth-param attributes MAY be used as well.

"realm":: A realm attribute MAY be included to indicate the scope of protection in the manner described in . The realm attribute MUST NOT appear more than once.
"scope":: The scope attribute is defined in . The scope attribute is a space-delimited set of case-sensitive scope values indicating the required scope of the access token for accessing the requested resource. Scope values are implementation defined; there is no centralized registry for them, and allowed values are defined by the authorization server. The order of scope values is not significant. In some cases, the scope value will be used when requesting a new access token with sufficient scope of access to utilize the protected resource. Use of the scope attribute is OPTIONAL. The scope attribute MUST NOT appear more than once. The scope value is intended for programmatic use and is not meant to be displayed to end-users. Two example scope values follow; these are taken from the OpenID Connect and the Open Authentication Technology Committee (OATC) Online Multimedia Authorization Protocol OAuth 2.0 use cases, respectively:
"error":: If the protected resource request included an access token and failed authentication, the resource server SHOULD include the error attribute to provide the client with the reason why the access request was declined. The parameter value is described in .
"error_description":: The resource server MAY include the error_description attribute to provide developers with a human-readable explanation that is not meant to be displayed to end-users.
"error_uri":: The resource server MAY include the error_uri attribute with an absolute URI identifying a human-readable web page explaining the error.

The error, error_description, and error_uri attributes MUST NOT appear more than once. Values for the scope attribute (specified in ) MUST NOT include characters outside the set %x21 / %x23-5B / %x5D-7E for representing scope values and %x20 for delimiters between scope values. Values for the error and error_description attributes (specified in and ) MUST NOT include characters outside the set %x20-21 / %x23-5B / %x5D-7E. Values for the error_uri attribute (specified in ) MUST conform to the URI-reference syntax and thus MUST NOT include characters outside the set %x21 / %x23-5B / %x5D-7E.

Error Codes When a request fails, the resource server responds using the appropriate HTTP status code (typically, 400, 401, 403, or 405) and includes one of the following error codes in the response:

"invalid_request":: The request is missing a required parameter, includes an unsupported parameter or parameter value, repeats the same parameter, uses more than one method for including an access token, or is otherwise malformed. The resource server SHOULD respond with the 400 (Bad Request) status code.
"invalid_token":: The access token provided is expired, revoked, malformed, or invalid for other reasons. The resource server SHOULD respond with the 401 (Unauthorized) status code. The client MAY request a new access token and retry the protected resource request.
"insufficient_scope":: The request requires higher privileges (scopes) than provided by the scopes granted to the client and represented by the access token. The resource server SHOULD respond with the 403 (Forbidden) status code and MAY include the scope attribute with the scope necessary to access the protected resource.

Extensions may define additional error codes or specify additional circumstances in which the above error codes are returned. If the request lacks any authentication information (e.g., the client was unaware that authentication is necessary or attempted using an unsupported authentication method), the resource server SHOULD NOT include an error code or other error information. For example: And in response to a protected resource request with an authentication attempt using an expired access token:

Extensibility

Defining Access Token Types Access token types can be defined in one of two ways: by registering them in the "OAuth Access Token Types" registry (following the procedures in ) or by using a unique absolute URI as the name.

Registered Access Token Types establishes a common registry, the "OAuth Extensions Error Registry" (), for error values to be shared among OAuth token authentication schemes. New authentication schemes designed primarily for OAuth token authentication SHOULD define a mechanism for providing an error status code to the client, in which the error values allowed are registered in the "OAuth Extensions Error Registry". Such schemes MAY limit the set of valid error codes to a subset of the registered values. If the error code is returned using a named parameter, the parameter name SHOULD be error. Other schemes capable of being used for OAuth token authentication, but not primarily designed for that purpose, MAY bind their error values to the registry in the same manner. New authentication schemes MAY choose to also specify the use of the error_description and error_uri parameters to return error information in a manner parallel to their usage in this specification. Type names MUST conform to the type-name ABNF. If the type definition includes a new HTTP authentication scheme, the type name SHOULD be identical to the HTTP authentication scheme name (as defined in ). The token type example is reserved for use in examples.

Vendor-Specific Access Token Types Types utilizing a URI name SHOULD be limited to vendor-specific implementations that are not commonly applicable and are specific to the implementation details of the resource server where they are used. All other types MUST be registered.

Defining New Endpoint Parameters New request or response parameters for use with the authorization endpoint or the token endpoint are defined and registered in the "OAuth Parameters" registry following the procedure in . Parameter names MUST conform to the param-name ABNF, and parameter value syntax MUST be well-defined (e.g., using ABNF or a reference to the syntax of an existing parameter). Unregistered vendor-specific parameter extensions that are not commonly applicable and that are specific to the implementation details of the authorization server where they are used SHOULD utilize a vendor-specific prefix that is not likely to conflict with other registered values (e.g., begin with companyname_).

Defining New Authorization Grant Types New authorization grant types can be defined by assigning them a unique absolute URI for use with the grant_type parameter. If the extension grant type requires additional token endpoint parameters, they MUST be registered in the "OAuth Parameters" registry as described by .

Defining New Authorization Endpoint Response Types New response types for use with the authorization endpoint are defined and registered in the "OAuth Authorization Endpoint Response Types" registry following the procedure in . Response type names MUST conform to the response-type ABNF. If a response type contains one or more space characters (%x20), it is compared as a space-delimited set of values in which the order of values does not matter. Only one order of values can be registered, which covers all other arrangements of the same set of values. For example, an extension can define and register the code other_token response type. Once registered, the same combination cannot be registered as other_token code, but both values can be used to denote the same response type.

Defining Additional Error Codes In cases where protocol extensions (i.e., access token types, extension parameters, or extension grant types) require additional error codes to be used with the authorization code grant error response (), the token error response (), or the resource access error response (), such error codes MAY be defined. Extension error codes MUST be registered (following the procedures in ) if the extension with which they are used is a registered access token type, a registered endpoint parameter, or an extension grant type. Error codes used with unregistered extensions MAY be registered. Error codes MUST conform to the error ABNF and SHOULD be prefixed by an identifying name when possible. For example, an error identifying an invalid value of the extension parameter example SHOULD be named example_invalid.

Security Considerations As a flexible and extensible framework, OAuth's security considerations depend on many factors. The following sections provide implementers with security guidelines focused on the three client profiles described in : web application, browser-based application, and native application. A comprehensive OAuth security model and analysis, as well as background for the protocol design, is provided by and .

Access Token Security Considerations

Security Threats The following list presents several common threats against protocols utilizing some form of tokens. This list of threats was originally derived from NIST Special Publication 800-63-1 , as described in .

Access Token Manufacture/Modification An attacker may generate a bogus access token or modify the token contents (such as the authentication or attribute statements) of an existing token, causing the resource server to grant inappropriate access to the client. For example, an attacker may modify the token to extend the validity period; a malicious client may modify the assertion to gain access to information that they should not be able to view.

Access Token Information Disclosure Access tokens may contain authentication and attribute statements that include sensitive information. If the client should be prevented from observing the contents of the access token, content encryption MUST be applied. Since cookies are by default transmitted in cleartext, any information contained in them is at risk of disclosure: Bearer tokens MUST NOT be stored in cookies that can be sent in the clear. See Sections 7 and 8 of for security considerations about cookies.

Access Token Redirect An attacker uses an access token generated for consumption by one resource server to gain access to a different resource server that mistakenly believes the token to be for it.

Access Token Replay An attacker attempts to use an access token that has already been used with that resource server in the past.

Threat Mitigation A large range of threats can be mitigated by protecting the contents of the access token by using a digital signature and by following best practices for signing key management such as periodic key rotation. Alternatively, a bearer token can contain a reference to authorization information, rather than encoding the information directly. Using a reference may require an extra interaction between a resource server and an authorization server to resolve the reference to the authorization information. The mechanics of such an interaction are not defined by this specification, but one such mechanism is defined in Token Introspection . This document does not specify the encoding or the contents of the access token; hence, detailed recommendations about the means of guaranteeing access token integrity protection are outside the scope of this specification. One example of an encoding and signing mechanism for access tokens is described in the JSON Web Token Profile for Access Tokens . To deal with access token redirects, it is important for the authorization server to include the identity of the intended recipients (the audience), typically a single resource server (or a list of resource servers), in the token. Restricting the use of the token to a specific scope is also RECOMMENDED. provides information on protecting against access token disclosure and on providing confidentiality and integrity for the communications among the client, resource server, and authorization server.

Summary of Recommendations

Safeguard Bearer Tokens Client implementations MUST ensure that bearer tokens are not leaked to unintended parties, as those parties would be able to use them to gain access to protected resources. This is the primary security consideration when using bearer tokens and underlies all the more specific recommendations that follow.

Validate TLS Certificate Chains The client MUST validate the TLS certificate chain when making requests to protected resources. Failing to do so may enable DNS hijacking attacks to steal the token and gain unintended access.

Always Use TLS (https) Clients MUST always use TLS (https) or equivalent transport security when making requests with bearer tokens. Failing to do so exposes the token to numerous attacks that could give attackers unintended access.

Don't Store Bearer Tokens in HTTP Cookies Implementations MUST NOT store bearer tokens within cookies that can be sent in the clear (which is the default transmission mode for cookies). Implementations that do store bearer tokens in cookies MUST take precautions against cross-site request forgery.

Issue Short-Lived Bearer Tokens Authorization servers SHOULD issue short-lived bearer tokens, particularly when issuing tokens to clients that run within a web browser or other environments where information leakage may occur. Using short-lived bearer tokens can reduce the impact of their leakage.

Issue Scoped Bearer Tokens Authorization servers SHOULD issue bearer tokens that contain an audience restriction, scoping their use to the intended resource server or set of resource servers.

Don't Pass Bearer Tokens in Page URLs Bearer tokens MUST NOT be passed in page URLs (for example, as query string parameters). Instead, bearer tokens SHOULD be passed in HTTP header fields or message content for which confidentiality measures are taken. Browsers, web servers, and other software may not adequately secure URLs in the browser history, web server logs, and other data structures. If bearer tokens are passed in page URLs, attackers might be able to steal them from the history data, logs, or other unsecured locations.

Access Token Privilege Restriction The client SHOULD request access tokens with the minimal scope necessary. The authorization server SHOULD take the client identity into account when choosing how to honor the requested scope and MAY issue an access token with fewer scopes than requested. The privileges associated with an access token SHOULD be restricted to the minimum required for the particular application or use case. This prevents clients from exceeding the privileges authorized by the resource owner. It also prevents users from exceeding their privileges authorized by the respective security policy. Privilege restrictions also help to reduce the impact of access token leakage. In particular, access tokens SHOULD be restricted to certain resource servers (audience restriction), preferably to a single resource server. To put this into effect, the authorization server associates the access token with certain resource servers, and every resource server is obliged to verify, for every request, whether the access token sent with that request was meant to be used for that particular resource server. If not, the resource server MUST refuse to serve the respective request. Clients and authorization servers MAY utilize the parameters scope or resource as specified in this document and , respectively, to determine the resource server they want to access. Additionally, access tokens SHOULD be restricted to certain resources and actions on resource servers or resources. To put this into effect, the authorization server associates the access token with the respective resource and actions, and every resource server is obliged to verify, for every request, whether the access token sent with that request was meant to be used for that particular action on the particular resource. If not, the resource server MUST refuse to serve the respective request. Clients and authorization servers MAY utilize the parameters scope and authorization_details as specified in to determine those resources and/or actions. The privileges associated with an access token represent the authorization granted to the client, and are not necessarily the only factor in an access control decision. A resource server may apply additional authorization logic, such as evaluating the resource owner's own permissions on a particular resource, and may deny a request even when the access token carries the scopes required for it. Access tokens may also convey authorization information beyond the scope of access delegated to the client, such as roles or entitlements of the resource owner. Such mechanisms are out of scope for this specification.

Client Authentication Depending on the overall process of client registration and credential lifecycle management, this may affect the confidence an authorization server has in a particular client. For example, authentication of a dynamically registered client does not prove the identity of the client; it only ensures that repeated requests to the authorization server were made from the same client instance. Such clients may be limited in terms of which scopes they are allowed to request, or may have other limitations such as shorter token lifetimes. In contrast, if a registered application's developer has had their identity verified and has signed a contract, and the application has been issued a client secret that is only used in a secure backend service, the authorization server might allow this client to request more sensitive scopes or to be issued longer-lasting tokens.

Client Impersonation If a confidential client has its credentials stolen, a malicious client can impersonate the client and obtain access to protected resources. The authorization server SHOULD require active resource owner interaction and provide the resource owner with information about the client and the requested authorization scope and lifetime. It is up to the resource owner to review the information in the context of the current client and to authorize or deny the request. The authorization server SHOULD NOT process repeated authorization requests automatically (without active resource owner interaction) without authenticating the client or relying on other measures to ensure that the repeated request comes from the original client and not an impersonator.

Impersonation of Native Apps As stated above, the authorization server SHOULD NOT process authorization requests automatically without user consent or interaction, except when the identity of the client can be assured. This includes the case where the user has previously approved an authorization request for a given client ID -- unless the identity of the client can be proven, the request SHOULD be processed as if no previous request had been approved. Measures such as claimed https scheme redirects provide stronger assurance than private-use URI schemes that the authorization response is delivered to the intended app, and authorization servers may take this into account when deciding whether to process a repeated authorization request automatically. Such measures do not authenticate the client, and do not make the client a confidential client. Some operating systems may offer alternative platform-specific identity features that may be used similarly, as appropriate.

Impersonation of Browser-Based Applications Authorization servers restrict redirect URIs to a fixed set of URIs, preventing the use of wildcard domains, wildcard paths, or wildcard query string components as described in . When a client uses an absolute https URI as a redirect URI, an exact match may be accepted by authorization servers as proof of identity of a browser-based application for the purpose of deciding whether to process an authorization request automatically when a previous request for the same client_id has already been approved.

Client Impersonating Resource Owner Resource servers may make access control decisions based on the identity of a resource owner for which an access token was issued, or based on the identity of a client in the client credentials grant. If both options are possible, depending on the details of the implementation, a client's identity may be mistaken for the identity of a resource owner. For example, if a client is able to choose its own client_id during registration with the authorization server, a malicious client may set it to a value identifying an end-user (e.g., a sub value if OpenID Connect is used). If the resource server cannot properly distinguish between access tokens issued to clients and access tokens issued to end-users, the client may then be able to access resources of the end-user. If the authorization server has a common namespace for client IDs and user identifiers, causing the resource server to be unable to distinguish an access token authorized by a resource owner from an access token authorized by a client itself, authorization servers SHOULD NOT allow clients to influence their client_id or any other claim if that can cause confusion with a genuine resource owner. Where this cannot be avoided, authorization servers MUST provide other means for the resource server to distinguish between the two types of access tokens.

Authorization Code Security Considerations

Authorization Code Injection Authorization code injection is an attack in which the client receives an authorization code from the attacker in its redirect URI instead of the authorization code from the legitimate authorization server. Without protections in place, there is no mechanism by which the client can know that the attack has taken place. Authorization code injection can lead to both the attacker obtaining access to a victim's account and a victim accidentally gaining access to the attacker's account.

Countermeasures To prevent injection of authorization codes into the client, using code_challenge and code_verifier is REQUIRED for clients, and authorization servers MUST enforce their use, unless both of the following criteria are met:

The client is a confidential client.
In the specific deployment and the specific request, there is reasonable assurance by the authorization server that the client implements the OpenID Connect nonce mechanism properly.

In this case, using and enforcing code_challenge and code_verifier is still RECOMMENDED. The code_challenge or OpenID Connect nonce value MUST be transaction-specific and securely bound to the client and the user agent in which the transaction was started. If a transaction leads to an error, fresh values for code_challenge or nonce MUST be chosen. Relying on the client to validate the OpenID Connect nonce parameter means the authorization server has no way to confirm that the client has actually protected itself against authorization code injection attacks. If an attacker is able to inject an authorization code into a client, the client would still exchange the injected authorization code and obtain tokens, and would only later reject the ID token after validating the nonce and seeing that it doesn't match. In contrast, the authorization server enforcing the code_challenge and code_verifier parameters provides stronger security, since the authorization server is able to recognize the authorization code injection attack preemptively and avoid issuing any tokens in the first place. Historical note: Although PKCE (where the code_challenge and code_verifier parameters were created) was originally designed as a mechanism to protect native apps from authorization code exfiltration attacks, all kinds of OAuth clients, including web applications and other confidential clients, are susceptible to authorization code injection attacks, which are addressed by the code_challenge and code_verifier mechanism.

PKCE "plain" Code Challenge Method The plain code challenge method, defined in , is explicitly forbidden in OAuth 2.1. The plain method offers no protection against authorization code interception by attackers who can read the authorization request (Attacker A4 in ), as the code verifier is transmitted in plaintext in the authorization request. Historical arguments for supporting the plain method (devices lacking cryptographic hashing capabilities) are obsoleted by OAuth 2.1's requirement for TLS 1.2+, which mandates SHA-256 support for certificate validation. Any device capable of implementing OAuth 2.1 necessarily supports SHA-256. Authorization servers that support the plain code challenge method create an unverifiable downgrade attack vector, as servers cannot distinguish legitimate constrained clients from attacker-modified requests claiming to be constrained. Deployments with existing clients that cannot support S256 SHOULD issue extended-lifetime refresh tokens before discontinuing support for legacy authorization methods, as the refresh token grant () does not require PKCE.

Reuse of Authorization Codes Several types of attacks are possible if authorization codes can be used more than once. As described in , the authorization server must reject a token request and revoke any issued tokens when receiving a second valid request with an authorization code that has already been used to issue an access token. If an attacker is able to exfiltrate an authorization code and use it before the legitimate client, the attacker will obtain the access token and the legitimate client will not. Revoking any issued tokens means the attacker's tokens will then be revoked, stopping the attack from proceeding any further. However, the authorization server should only revoke issued tokens if the request containing the authorization code is also valid, including any other parameters such as the code_verifier and client authentication. The authorization server SHOULD NOT revoke any issued tokens when receiving a replayed authorization code that contains invalid parameters. If it were to do so, this would create a denial-of-service opportunity for an attacker who is able to obtain an authorization code but unable to obtain the client authentication or code_verifier by sending an invalid authorization code request before the legitimate client and thereby revoking the legitimate client's tokens once it makes the valid request.

307 (Temporary Redirect) Status Code An authorization server that redirects a request that potentially contains user credentials MUST NOT use the 307 (Temporary Redirect) status code () for redirection. If an HTTP redirection (and not, for example, JavaScript) is used for such a request, the AS SHOULD use the 303 (See Other) status code. At the authorization endpoint, a typical protocol flow is that the AS prompts the user to enter their credentials in a form that is then submitted (using the POST method) back to the authorization server. The AS checks the credentials and, if successful, redirects the user agent to the client's redirect URI. If the 307 status code were used for redirection, the user agent would send the user credentials via a POST request to the client. This discloses the sensitive credentials to the client. If the client is malicious, it can use the credentials to impersonate the user at the AS. The behavior might be unexpected for developers, but is defined in . This status code does not require the user agent to rewrite the POST request to a GET request and thereby drop the form data in the POST request content. In HTTP , only the 303 status code unambiguously enforces rewriting the HTTP POST request to an HTTP GET request. For all other status codes, including the popular 302 (Found), user agents can opt not to rewrite POST to GET requests and therefore reveal the user credentials to the client. (In practice, however, most user agents will only show this behavior for 307 redirects.)

Ensuring Endpoint Authenticity The risk related to man-in-the-middle attacks is mitigated by the mandatory use of channel security mechanisms such as TLS () for communicating with the authorization and token endpoints. See for further details.

Credentials-Guessing Attacks The authorization server MUST prevent attackers from guessing access tokens, authorization codes, refresh tokens, resource owner passwords, and client credentials. The probability of an attacker guessing generated tokens (and other credentials not intended for handling by end-users) MUST be less than or equal to 2^(-128) and SHOULD be less than or equal to 2^(-160). The authorization server MUST utilize other means to protect credentials intended for use by end-users.

Phishing Attacks Wide deployment of this and similar protocols may cause end-users to become inured to the practice of being redirected to websites where they are asked to enter their passwords. If end-users are not careful to verify the authenticity of these websites before entering their credentials, it will be possible for attackers to exploit this practice to steal resource owners' passwords and other phishable credentials, such as OTPs. Service providers should attempt to educate end-users about the risks phishing attacks pose and should provide mechanisms that make it easy for end-users to confirm the authenticity of their sites, such as using phishing-resistant authenticators, as phishing-resistant authenticators will offer a credential to log in to a certain site to the user only if the platform has successfully verified the site's origin. Client developers should consider the security implications of how they interact with the user agent (e.g., external, embedded), and the ability of the end-user to verify the authenticity of the authorization server. See for further details on mitigating the risk of phishing attacks.

Consent Phishing As authorization servers deploy phishing-resistant authentication methods, attackers may pivot to targeting the authorization step rather than the authentication step. In a consent phishing attack, an attacker registers an attacker-controlled client with the authorization server, crafts an authorization request with a scope value targeting the victim's resources, and delivers the resulting authorization endpoint URL to the victim through a phishing message. Because the authorization request is processed by the legitimate authorization server, the resource owner authenticates normally, including through any phishing-resistant factors, and is then presented with an authorization prompt that appears trustworthy. If the resource owner grants the request, the attacker receives an authorization code or access token granting access to the victim's resources. Critically, phishing-resistant authenticators do not protect against consent phishing. The resource owner successfully authenticates to the legitimate authorization server. The attack exploits the subsequent consent step, not the authentication step. Authorization servers SHOULD consider enforcing controls over client registration, including restricting which scopes a given client is permitted to request. Where possible, authorization servers SHOULD verify the identity of client developers prior to granting access to sensitive scopes. Authorization servers SHOULD present resource owners with clear and meaningful information during the authorization prompt, including the client name, the developer or organization that registered it, and the specific scopes being requested, so that resource owners can make an informed decision before granting access. In scenarios where client pre-registration is not possible, such as when using Dynamic Client Registration , or when the client metadata may be provided by an outside party such as when using a Client ID Metadata Document , authorization servers SHOULD take additional measures to verify that the user understands the client they are authorizing. Authorization servers SHOULD allow administrators and resource owners to view the set of clients that have been granted access to their resources and to revoke those grants (see ), thereby limiting the window of exposure if a resource owner is deceived into approving a malicious authorization request.

Cross-Site Request Forgery An attacker might attempt to inject a request to the redirect URI of the legitimate client on the victim's device, e.g., to cause the client to access resources under the attacker's control. This is a variant of an attack known as Cross-Site Request Forgery (CSRF). The traditional countermeasure is that clients pass a random value, also known as a CSRF token, in the state parameter that links the request to the redirect URI to the user agent session. This countermeasure is described in detail in . The same protection is provided by the code_verifier parameter or the OpenID Connect nonce value. When using code_verifier instead of state or nonce for CSRF protection, it is important to note that:

Clients MUST ensure that the AS supports the code_challenge_method intended to be used by the client. If an authorization server does not support the requested method, state or nonce MUST be used for CSRF protection instead.
If state is used for carrying application state, and the integrity of its contents is a concern, clients MUST protect state against tampering and swapping. This can be achieved by binding the contents of state to the browser session and/or using signed or encrypted state values .

The AS therefore MUST provide a way to detect its supported code challenge methods, either via AS metadata according to or via a deployment-specific way to ensure or determine support.

Clickjacking As described in , the authorization request is susceptible to clickjacking attacks, also called user interface redressing. In such an attack, an attacker embeds the authorization endpoint user interface in an innocuous context. A user who believes they are interacting with that context, for example, by clicking on buttons, inadvertently interacts with the authorization endpoint user interface instead. The opposite can be achieved as well: a user who believes they are interacting with the authorization endpoint might inadvertently type a password into an attacker-provided input field overlaid on the original user interface. Clickjacking attacks can be designed such that users can hardly notice the attack, for example, by using almost invisible iframes overlaid on top of other elements. An attacker can use this vector to obtain the user's authentication credentials, change the scope of access granted to the client, and potentially access the user's resources. Authorization servers MUST prevent clickjacking attacks. Multiple countermeasures are described in , including the use of the X-Frame-Options response header field and frame-busting JavaScript. In addition to those, authorization servers SHOULD also use Content Security Policy (CSP) level 2 or greater. To be effective, CSP must be used on the authorization endpoint and, if applicable, other endpoints used to authenticate the user and authorize the client (e.g., the device authorization endpoint, login pages, error pages, etc.). This prevents framing by unauthorized origins in user agents that support CSP. The client MAY permit being framed by an origin other than the one used in its redirection endpoint. For this reason, authorization servers SHOULD allow administrators to configure allowed origins for particular clients and/or for clients to register these dynamically. Using CSP allows authorization servers to specify multiple origins in a single response header field and to constrain these using flexible patterns (see for details). Level 2 of this standard provides a robust mechanism for protecting against clickjacking by using policies that restrict the origin of frames (using frame-ancestors) together with those that restrict the sources of scripts allowed to execute on an HTML page (by using script-src). A non-normative example of such a policy is shown in the following listing: Because some user agents do not support , this technique SHOULD be combined with others, including those described in , unless such legacy user agents are explicitly unsupported by the authorization server. Even in such cases, additional countermeasures SHOULD still be employed.

Injection and Input Validation An injection attack occurs when an input or otherwise external variable is used by an application unsanitized and causes modification to the application logic. This may allow an attacker to gain access to the application device or its data, cause denial of service, or introduce a wide range of malicious side effects. The authorization server and client MUST treat parameters received as potentially malicious external input and apply appropriate protections, in particular, the access token, and values of the the state and redirect_uri parameters.

Open Redirection An open redirector is an endpoint that forwards a user's browser to an arbitrary URI obtained from a query parameter. Such endpoints are sometimes implemented, for example, to show a message before a user is then redirected to an external website, or to redirect users back to a URL they were intending to visit before being interrupted, e.g., by a login prompt. The following attacks can occur when an AS or client has an open redirector.

Client as Open Redirector Clients MUST NOT expose open redirectors. Attackers may use open redirectors to produce URLs pointing to the client and utilize them to exfiltrate authorization codes, as described in . Another abuse case is to produce URLs that appear to point to the client. This might trick users into trusting the URL and following it in their browser. This can be abused for phishing. In order to prevent open redirection, clients should only redirect if the target URLs are included in an allowlist or if the origin and integrity of a request can be authenticated. Countermeasures against open redirection are described by OWASP .

Authorization Server as Open Redirector Just as with clients, attackers could try to utilize a user's trust in the authorization server (and its URL in particular) for performing phishing attacks. OAuth authorization servers regularly redirect users to other websites (the clients), but must do so safely. already prevents open redirects by stating that the authorization server MUST NOT automatically redirect the user agent in the case of an invalid combination of client_id and redirect_uri. However, an attacker could also utilize a correctly registered redirect URI to perform phishing attacks. The attacker could, for example, register a client via Dynamic Client Registration and execute one of the following attacks:

Intentionally send an erroneous authorization request, e.g., by using an invalid scope value, thus instructing the authorization server to redirect the user agent to its phishing site.
Intentionally send a valid authorization request with client_id and redirect_uri controlled by the attacker. After the user authenticates, the authorization server prompts the user to provide consent to the request. If the user notices an issue with the request and declines the request, the authorization server still redirects the user agent to the phishing site. In this case, the user agent will be redirected to the phishing site regardless of the action taken by the user.
Intentionally send a valid silent authentication request (prompt=none) with client_id and redirect_uri controlled by the attacker. In this case, the authorization server will automatically redirect the user agent to the phishing site.

The authorization server MUST take precautions to prevent these threats. The authorization server MUST always authenticate the user first and, with the exception of the silent authentication use case, prompt the user for credentials when needed, before redirecting the user. Based on its risk assessment, the authorization server needs to decide whether it can trust the redirect URI or not. It could take into account URI analytics done internally or through some external service to evaluate the credibility and trustworthiness of the content behind the URI, and the source of the redirect URI and other client data. The authorization server SHOULD only automatically redirect the user agent if it trusts the redirect URI. If the URI is not trusted, the authorization server MAY inform the user and rely on the user to make the correct decision.

Transport Security In some deployments, including those utilizing load balancers, the TLS connection to the resource server terminates prior to the actual server that provides the resource. This could leave the token unprotected between the front-end server where the TLS connection terminates and the back-end server that provides the resource. In such deployments, sufficient measures MUST be employed to ensure confidentiality of the access token between the front-end and back-end servers; encryption of the token is one such possible measure. See for further information.

Authorization Server Mix-Up Mitigation Mix-up is an attack on scenarios where an OAuth client interacts with two or more authorization servers and at least one authorization server is under the control of the attacker. This can be the case, for example, if the attacker uses dynamic registration to register the client at their own authorization server or if an authorization server becomes compromised. When an OAuth client can only interact with one authorization server, a mix-up defense is not required. In scenarios where an OAuth client interacts with two or more authorization servers, however, clients MUST prevent mix-up attacks. Two different methods are discussed in the following sections. For both defenses, clients MUST store, for each authorization request, the issuer to which they sent the authorization request, bind this information to the user agent, and check that the authorization response was received from the correct issuer. Clients MUST ensure that the subsequent access token request, if applicable, is sent to the same issuer. The issuer serves, via the associated metadata, as an abstract identifier for the combination of the authorization endpoint and token endpoint that are to be used in the flow. If an issuer identifier is not available, for example, if neither OAuth 2.0 Authorization Server Metadata nor OpenID Connect Discovery is used, a different unique identifier for this tuple or the tuple itself can be used instead. For brevity of presentation, such a deployment-specific identifier will be subsumed under the issuer (or issuer identifier) in the following. Note: Just storing the authorization server URL is not sufficient to identify mix-up attacks. An attacker might declare an uncompromised AS's authorization endpoint URL as "their" AS URL, but declare a token endpoint under their own control. See for a detailed description of several types of mix-up attacks.

Mix-Up Defense via Issuer Identification This defense requires that the client compare the issuer identifier value that the authorization server sends in the authorization response to the client in the iss parameter as described in . When receiving the authorization response, the client MUST compare the received issuer identifier to the stored issuer identifier. If there is a mismatch, the client MUST abort the interaction. The iss value MUST be evaluated according to . While this defense may require using an additional parameter to transport the issuer information, it is a robust and relatively simple defense against mix-up.

Mix-Up Defense via Distinct Redirect URIs For this defense, clients MUST use a distinct redirect URI for each issuer they interact with. Clients MUST check that the authorization response was received from the correct issuer by comparing the distinct redirect URI for the issuer to the URI at which the authorization response was received. If there is a mismatch, the client MUST abort the flow. While this defense builds upon existing OAuth functionality, it cannot be used in scenarios where clients only register once for the use of many different issuers (as in some open banking schemes), and, due to the tight integration with the client registration, it is harder to deploy automatically. Furthermore, an attacker might be able to circumvent the protection offered by this defense by registering a new client with the "honest" AS using the redirect URI that the client assigned to the attacker's AS. The attacker could then run the attack as described above, replacing the client ID with the client ID of their newly created client. This defense SHOULD therefore only be used if other options are not available.

Native Applications Native applications are clients installed and executed on the device used by the resource owner (e.g., desktop applications or native mobile applications). Native applications require special consideration related to security, platform capabilities, and overall end-user experience. The guidance in this section is primarily in the context of native mobile apps as opposed to desktop apps. The native mobile platforms have matured more than the desktop platforms in terms of the capabilities provided to app developers relevant to the OAuth flows described here. While the guidance is primarily focused on mobile apps, much of it can generally apply to desktop apps as well. The authorization endpoint requires interaction between the client and the resource owner's user agent. The best current practice is to perform the OAuth authorization request in an external user agent (typically the browser) rather than an embedded user agent (such as one implemented with web-views). The native application can capture the response from the authorization server in several different ways, each with different security properties. For example, using a redirect URI with an "app-claimed URL" or custom URL scheme registered with the operating system to invoke the client as the handler, manual copy-and-paste of the credentials, running a local web server, installing a user agent extension, or providing a redirect URI identifying a server-hosted resource under the client's control, which in turn makes the response available to the native application. Previously, it was common for native apps to use embedded user agents (commonly implemented with web-views) for OAuth authorization requests. That approach has many drawbacks, including the host app being able to copy user credentials and cookies as well as the user needing to authenticate from scratch in each app. See for a deeper analysis of the drawbacks of using embedded user agents for OAuth. Native app authorization requests that use the system browser are more secure and can take advantage of the user's authentication state on the device. Being able to use the existing authentication session in the browser enables single sign-on, as users don't need to authenticate to the authorization server each time they use a new app (unless required by the authorization server policy). Supporting authorization flows between a native app and the browser is possible without changing the OAuth protocol itself, as the OAuth authorization request and response are already defined in terms of URIs. This encompasses URIs that can be used for inter-app communication. Some OAuth server implementations that assume all clients are confidential web clients will need to add an understanding of public native app clients and the types of redirect URIs they use to support these recommendations.

Client Authentication of Native Apps Secrets that are statically included as part of an app distributed to multiple users are not confidential secrets, as one user may inspect their copy and learn the shared secret. For this reason, authorization servers MUST NOT require client authentication of native app clients using a shared secret, as doing so serves no purpose beyond client identification, which is already provided by the client_id request parameter. Authorization servers that still require a statically included shared secret for native app clients MUST treat the client as a public client (as defined in ) and not accept the secret as proof of the client's identity. Without additional measures, such clients are subject to client impersonation (see ).

Registration of Native App Clients Except when using a mechanism like Dynamic Client Registration to provision per-instance credentials, native apps are classified as public clients, as defined in , and MUST be registered with the authorization server as such. Authorization servers MUST record the client type in the client registration details in order to identify and process requests accordingly.

Native App Attestation The draft specification defines a mechanism that can be used by a native app to obtain a key-bound attestation to authenticate to an authorization server or resource server. This can provide a higher level of assurance of a mobile app's identity.

Using Inter-App URI Communication for OAuth in Native Apps Just as URIs are used for OAuth on the web to initiate the authorization request and return the authorization response to the requesting website, URIs can be used by native apps to initiate the authorization request in the device's browser and return the response to the requesting native app. By adopting the same methods used on the web for OAuth, benefits seen in the web context, such as the usability of a single sign-on session and the security of a separate authentication context are likewise gained in the native app context. Reusing the same approach also reduces the implementation complexity and increases interoperability by relying on standards-based web flows that are not specific to a particular platform. Native apps MUST use an external user agent to perform OAuth authorization requests. This is achieved by opening the authorization request in the browser (detailed in ) and using a redirect URI that will return the authorization response to the native app (defined in ).

Initiating the Authorization Request from a Native App Native apps needing user authorization create an authorization request URL with the authorization code grant type per using a redirect URI capable of being received by the native app. The function of the redirect URI for a native app authorization request is similar to that of a web-based authorization request. Rather than returning the authorization response to the OAuth client's server, the redirect URI used by a native app returns the response to the app. Several options for a redirect URI that will return the authorization response to the native app in different platforms are documented in . Any redirect URI that allows the app to receive the URI and inspect its parameters is viable. After constructing the authorization request URL, the app uses platform-specific APIs to open the URL in an external user agent. Typically, the external user agent used is the default browser, that is, the application configured for handling http and https scheme URIs on the system; however, different browser selection criteria and other categories of external user agents MAY be used. This specification focuses on the browser as the RECOMMENDED external user agent for native apps. An external user agent designed specifically for user authorization and capable of processing authorization requests and responses like a browser MAY also be used. Other external user agents, such as a native app provided by the authorization server, may meet the criteria set out in this specification, including using the same redirect URI properties, but their use is out of scope for this specification. Some platforms support a browser feature known as "in-app browser tabs", where an app can present a tab of the browser within the app context without switching apps, but still retain key benefits of the browser such as a shared authentication state and security context. On platforms where they are supported, it is RECOMMENDED, for usability reasons, that apps use in-app browser tabs for the authorization request.

Receiving the Authorization Response in a Native App There are several redirect URI options available to native apps for receiving the authorization response from the browser, the availability and user experience of which vary by platform.

Claimed "https" Scheme URI Redirection Some operating systems, in particular mobile operating systems, allow apps to claim https URIs (see ) in the domains they control. When the browser encounters a claimed URI, instead of the page being loaded in the browser, the native app is launched with the URI supplied as a launch parameter. Such URIs can be used as redirect URIs by native apps. They are indistinguishable to the authorization server from a regular web-based client redirect URI. An example is: As the redirect URI alone is not enough to distinguish public native app clients from confidential web clients, it is REQUIRED in that the client type be recorded during client registration to enable the server to determine the client type and act accordingly. App-claimed https scheme redirect URIs have some advantages compared to other native app redirect options in that the identity of the destination app is guaranteed to the authorization server by the operating system. For this reason, native apps SHOULD use them over the other options where possible.

Loopback Interface Redirection Native apps that are able to open a port on the loopback network interface without needing special permissions (typically, those on desktop operating systems) can use the loopback interface to receive the OAuth redirect. Loopback redirect URIs use the http scheme and are constructed with the loopback IP literal and whatever port the client is listening on. That is, http://127.0.0.1:{port}/{path} for IPv4, and http://[::1]:{port}/{path} for IPv6. An example redirect using the IPv4 loopback interface with a randomly assigned port: An example redirect using the IPv6 loopback interface with a randomly assigned port: While redirect URIs using the name localhost (i.e., http://localhost:{port}/{path}) function similarly to loopback IP redirects, the use of localhost is NOT RECOMMENDED. Specifying a redirect URI with the loopback IP literal rather than localhost avoids inadvertently listening on network interfaces other than the loopback interface. It is also less susceptible to client-side firewalls and misconfigured host name resolution on the user's device. The authorization server MUST allow any port to be specified at the time of the request for loopback IP redirect URIs, to accommodate clients that obtain an available ephemeral port from the operating system at the time of the request. Loopback interface redirect URIs may be susceptible to interception by other apps accessing the same loopback interface on some operating systems. Clients SHOULD NOT assume that the device supports a particular version of the Internet Protocol. It is RECOMMENDED that clients attempt to bind to the loopback interface using both IPv4 and IPv6 and use whichever is available.

Private-Use URI Scheme Redirection Many mobile and desktop computing platforms support inter-app communication via URIs by allowing apps to register private-use URI schemes (sometimes colloquially referred to as "custom URL schemes") like com.example.app. When the browser or another app attempts to load a URI with a private-use URI scheme, the app that registered it is launched to handle the request. Many environments that support private-use URI schemes do not provide a mechanism to claim a scheme and prevent other parties from using another application's scheme. As such, clients using private-use URI schemes are vulnerable to potential attacks on their redirect URIs, so this option should only be used if the previously mentioned more secure options are not available. To perform an authorization request with a private-use URI scheme redirect, the native app launches the browser with a standard authorization request, but one where the redirect URI utilizes a private-use URI scheme it registered with the operating system. When choosing a URI scheme to associate with the app, apps MUST use a URI scheme based on a domain name under their control, expressed in reverse order, as recommended by for private-use URI schemes. For example, an app that controls the domain name app.example.com can use com.example.app as its scheme. Some authorization servers assign client identifiers based on domain names, for example, client1234.usercontent.example.net, which can also be used as the domain name for the scheme when reversed in the same manner. A scheme such as myapp, however, would not meet this requirement, as it is not based on a domain name. When there are multiple apps by the same publisher, care must be taken so that each scheme is unique within that group. On platforms that use app identifiers based on reverse-order domain names, those identifiers can be reused as the private-use URI scheme for the OAuth redirect to help avoid this problem. Following the requirements of , as there is no naming authority for private-use URI scheme redirects, only a single slash (/) appears after the scheme component. A complete example of a redirect URI utilizing a private-use URI scheme is: When the authorization server completes the request, it redirects to the client's redirect URI as it would normally. As the redirect URI uses a private-use URI scheme, it results in the operating system launching the native app, passing in the URI as a launch parameter. Then, the native app uses normal processing for the authorization response.

Security Considerations in Native Apps

Embedded User Agents in Native Apps Embedded user agents are a technically possible method for authorizing native apps. These embedded user agents are unsafe for use by third parties to the authorization server by definition, as the app that hosts the embedded user agent can access the user's full authentication credentials, not just the OAuth authorization grant that was intended for the app. They are also typically sandboxed by the operating system, and mechanisms such as WebAuthn that rely on the web origin are disabled. In typical web-view-based implementations of embedded user agents, the host application can record every keystroke entered in the login form to capture usernames and passwords, automatically submit forms to bypass user consent, and copy session cookies and use them to perform authenticated actions as the user. Even when used by trusted apps belonging to the same party as the authorization server, embedded user agents violate the principle of least privilege by having access to more powerful credentials than they need, potentially increasing the attack surface. Encouraging users to enter credentials in an embedded user agent without the usual address bar and visible certificate validation features that browsers have makes it impossible for the user to know if they are signing in to the legitimate site; even when they are, it trains them that it's OK to enter credentials without validating the site first. Aside from the security concerns, embedded user agents do not share the authentication state with other apps or the browser, requiring the user to log in for every authorization request, which is often considered an inferior user experience.

Fake External User Agents in Native Apps The native app that is initiating the authorization request has a large degree of control over the user interface and can potentially present a fake external user agent, that is, an embedded user agent made to appear as an external user agent. When all good actors are using external user agents, the advantage is that it is possible for security experts to detect bad actors, as anyone faking an external user agent is provably bad. On the other hand, if good and bad actors alike are using embedded user agents, bad actors don't need to fake anything, making them harder to detect. Once a malicious app is detected, it may be possible to use this knowledge to block the app's signature in malware scanning software, take removal action (in the case of apps distributed by app stores), and take other steps to reduce the impact and spread of the malicious app. Authorization servers can also directly protect against fake external user agents by requiring an authentication factor only available to true external user agents. Users who are particularly concerned about their security when using in-app browser tabs may also take the additional step of opening the request in the full browser from the in-app browser tab and completing the authorization there, as most implementations of the in-app browser tab pattern offer such functionality.

Malicious External User Agents in Native Apps If a malicious app is able to configure itself as the default handler for https scheme URIs in the operating system, it will be able to intercept authorization requests that use the default browser and abuse this position of trust for malicious ends such as phishing the user. This attack is not confined to OAuth; a malicious app configured in this way would present a general and ongoing risk to the user beyond OAuth usage by native apps. Many operating systems mitigate this issue by requiring an explicit user action to change the default handler for http and https scheme URIs.

Loopback Redirect Considerations in Native Apps Loopback interface redirect URIs MAY use the http scheme (i.e., without TLS). This is acceptable for loopback interface redirect URIs as the HTTP request never leaves the device. Clients SHOULD open the network port only when starting the authorization request and close it once the response is returned. Clients SHOULD listen on the loopback network interface only, in order to avoid interference by other network actors. Clients SHOULD use loopback IP literals rather than the string localhost as described in .

Browser-Based Applications Browser-based applications are clients that run in a web browser, typically written in JavaScript, also known as "single-page apps". Because the application's code is delivered to and executed within the user agent, any code running in the application's origin has access to the same data and APIs as the application itself. These types of apps have particular security considerations similar to native apps. There are three architecture patterns available when building a browser-based application that uses OAuth to access protected resources, presented here in decreasing order of security:

the app relies on a backend component to handle all OAuth responsibilities and forwards all resource requests through that backend component, known as a "Backend for Frontend" or "BFF" ()
the app relies on a backend component to handle all OAuth responsibilities but calls resource servers directly using the access token, known as a "token-mediating backend" ()
the app is itself the OAuth client, handling all OAuth responsibilities in the browser ()

Each pattern offers a different trade-off between security and simplicity. See for the threat model of malicious JavaScript, a detailed analysis of which attacks each pattern does and does not withstand, and sequence diagrams of each pattern. Browser-based applications MUST use the authorization code grant () to obtain an access token. The Implicit grant and the Resource Owner Password Credentials grant, both of which were historically used by browser-based applications, are not defined in this specification and MUST NOT be used, as described in .

Backend for Frontend In this pattern, a backend component becomes the OAuth client for the browser-based application. The backend component obtains and manages tokens in the context of a cookie-based session with the browser, and forwards every resource request to the resource server after augmenting it with the appropriate access token. No tokens are exposed to the browser. The BFF MUST act as a confidential client () by establishing credentials with the authorization server, and MUST use the authorization code grant () to obtain an access token. See for the cookie security, Cross-Site Request Forgery, and proxy restriction requirements that apply to the BFF's interactions with the browser-based application.

Token-Mediating Backend In this pattern, a backend component becomes the OAuth client for the browser-based application and manages the refresh token in the context of a cookie-based session, but passes the access token to the browser-based app, which calls resource servers directly. The token-mediating backend MUST act as a confidential client () and MUST use the authorization code grant () to obtain an access token. See for the cookie security, Cross-Site Request Forgery, and access token scope requirements that apply to the token-mediating backend's interactions with the browser-based application.

Browser-Based OAuth Clients A browser-based application acting as the OAuth client itself is a public client, as defined in , and MUST be registered with the authorization server as such. In addition to the requirements that apply to all clients using the authorization code grant, in particular PKCE (), exact matching of registered redirect URIs (), and defenses against Cross-Site Request Forgery attacks on the redirect URI (), the requirements in this section apply.

Client Authentication of Browser-Based Applications Because a browser-based application's source code is delivered to the end user's browser, it cannot contain provisioned secrets. Secrets that are statically included as part of an application distributed to multiple users are not confidential secrets, as one user may inspect their copy and learn the shared secret. For this reason, authorization servers MUST NOT require client authentication of browser-based applications using a shared secret, as this serves no value beyond client identification which is already provided by the client_id request parameter. Authorization servers that still require a statically included shared secret for browser-based applications MUST treat the client as a public client (as defined in ), and not accept the secret as proof of the client's identity. Without additional measures, such clients are subject to client impersonation (see ).

Refresh Tokens for Browser-Based Applications For browser-based applications, the refresh token is a bearer token unless the app uses a mechanism such as DPoP . As a result, the risk of a leaked refresh token is greater than that of a leaked access token, since an attacker may be able to continue using the stolen refresh token to obtain new access tokens without being detected by the authorization server. Refresh tokens issued to browser-based applications are subject to the requirements in . In addition, authorization servers issuing refresh tokens to browser-based applications:

MUST either set a maximum lifetime on the refresh token, or expire the refresh token if it has not been used within some amount of time
MUST NOT, when issuing a rotated refresh token, extend the lifetime of the new refresh token beyond the lifetime of the initial refresh token, if the initial refresh token had a pre-established expiration time

Limiting the overall refresh token lifetime to the lifetime of the initial refresh token ensures a stolen refresh token cannot be used indefinitely. See for a worked example. Authorization servers SHOULD link the lifetime of the refresh token to the user's authenticated session with the authorization server, so that when the user logs out, previously issued refresh tokens become invalid. Authorization servers MAY set different policies for refresh token issuance, lifetime, and expiration for browser-based applications compared to other public clients.

In-Browser Communication in Browser-Based Applications It is common for a browser-based application to execute the OAuth flow in a secondary window, such as a pop-up or an iframe, rather than redirecting the primary window. If the app and the authorization server are invoked in different frames, they use in-browser communication techniques such as the postMessage API instead of top-level redirections. To guarantee the confidentiality and authenticity of these messages, both the initiator origin and the receiver origin of a postMessage MUST be verified using the mechanisms provided by the postMessage API. See for further details about the security of in-browser communication flows and the countermeasures that browser-based apps and authorization servers MUST apply to defend against these attacks.

Cross-Origin Requests in Browser-Based Applications A browser-based OAuth client uses browser APIs to send requests to the authorization server and the resource server. These requests are typically cross-origin requests, and are subject to the browser's restrictions on cross-origin communication. The authorization server and resource server MUST send the necessary CORS header fields to enable the app to make these requests, as described in . See for considerations on choosing a CORS policy.

Token Storage in Browser-Based Applications A browser-based application that handles access tokens or refresh tokens directly is responsible for storing them. None of the storage mechanisms available in the browser prevent an attacker who is able to execute code in the app's origin from obtaining a new set of tokens in the same way the app does, so no storage mechanism can fully mitigate token exfiltration. The choice of mechanism does affect the attacker's ability to obtain existing tokens from storage. See for a comparison of the available mechanisms. Storing tokens using the browser's JavaScript Cookie API is NOT RECOMMENDED. Because such a cookie is associated with the domain of the browser-based application, the browser will also send the token to the server hosting the app on subsequent requests, exposing the token beyond its intended recipient. This is different from the use of cookies by a BFF (), where the cookie is inaccessible to JavaScript and is intended to be sent to the backend. When a Service Worker or Web Worker is used to isolate tokens from the app's execution context, it MUST NOT store those tokens in a persistent storage API that is shared with the main window.

Security Considerations in Browser-Based Applications

Sender-Constrained Tokens in Browser-Based Applications The use of sender-constrained tokens (), for example using DPoP , enhances the security of both access tokens and refresh tokens issued to browser-based applications, as a stolen token is not usable without the corresponding private key. Note that this shifts the challenge of securely storing the token to securely storing the private key, and that it does not address an attacker's ability to obtain a new set of tokens by running a new flow. See for further details.

Reducing the Authority of Tokens in Browser-Based Applications Because tokens in a browser-based application are more exposed than in other architectures, the privilege restrictions described in are particularly important. Short access token lifetimes, minimal scopes, and restricting an access token to a single resource server all reduce the impact of a stolen token.

Isolating Browser-Based Applications Using Origins Many of the web's security mechanisms, including the browser's isolation of browsing contexts and the CORS restrictions described in , rely on origins, defined as the triple of scheme, hostname and port. Deploying more than one application in a single origin prevents an application from taking advantage of these restrictions, and makes security measures such as CORS harder to configure correctly. It is therefore a best practice to deploy no more than one application per origin.

Authorization Server Mix-Up in Browser-Based Applications Mix-up attacks are a particular threat to browser-based applications that support more than one authorization server. The countermeasures in apply.

Differences from OAuth 2.0 This draft consolidates the functionality in OAuth 2.0 , OAuth 2.0 for Native Apps , Proof Key for Code Exchange , OAuth 2.0 for Browser-Based Applications , OAuth Security Best Current Practice , and Bearer Token Usage . Where a later specification updates or obsoletes functionality found in the original , that functionality in this draft is updated with the normative changes described in that later specification, or removed entirely. The following is a non-normative list of changes from OAuth 2.0:

The authorization code grant is extended with the functionality from PKCE such that the default method of using the authorization code grant according to this specification requires the addition of the PKCE parameters
Redirect URIs must be compared using exact string matching as per
The Implicit grant (response_type=token) is omitted from this specification as per
The Resource Owner Password Credentials grant is omitted from this specification as per
Bearer token usage omits the use of bearer tokens in the query string of URIs as per
Refresh tokens for public clients must either be sender-constrained or one-time-use as per
Refresh tokens issued to browser-based applications have additional lifetime constraints as per
The token endpoint request containing an authorization code no longer contains the redirect_uri parameter
Authorization servers must support client credentials in the request content
The PKCE plain method is removed

An OAuth 2.0 client that does not use PKCE, relies on redirect URI pattern matching, or uses the Implicit or Resource Owner Password Credentials grants will not interoperate with an authorization server that enforces the requirements of this specification for that client (see ).

Removal of the OAuth 2.0 Implicit Grant The OAuth 2.0 Implicit grant is omitted from OAuth 2.1 as it was deprecated in . The intent of removing the Implicit grant is to no longer issue access tokens in the authorization response, as such tokens are vulnerable to leakage and injection and cannot be sender-constrained to a client. This behavior was indicated by clients using the response_type=token parameter. This value for the response_type parameter is no longer defined in OAuth 2.1. Removal of response_type=token does not have an effect on other extension response types returning other artifacts from the authorization endpoint, for example, response_type=id_token defined by .

Redirect URI Parameter in Token Request In OAuth 2.0, the request to the token endpoint in the authorization code flow () contains an optional redirect_uri parameter. The parameter was intended to prevent an authorization code injection attack and was required if the redirect_uri parameter was sent in the original authorization request. The authorization request only required the redirect_uri parameter if multiple redirect URIs were registered for the specific client. However, in practice, many authorization server implementations required the redirect_uri parameter in the authorization request even if only one was registered, leading the redirect_uri parameter to be required at the token endpoint as well. In OAuth 2.1, authorization code injection is prevented by the code_challenge and code_verifier parameters, so including the redirect_uri parameter in the token request serves no purpose. As such, it has been removed. To provide backward compatibility, an authorization server that supports both OAuth 2.0 and OAuth 2.1 clients MUST allow clients to send the redirect_uri parameter in the token request (), and MUST enforce the parameter as described in . The authorization server can use the client_id in the request to determine whether to enforce this behavior for the specific client that it knows will be using the older OAuth 2.0 behavior (see ). A client following only the OAuth 2.1 recommendations will not send the redirect_uri in the token request, and therefore will not be compatible with an authorization server that expects the parameter in the token request.

IANA Considerations This document does not require any IANA actions. All referenced registries are defined by and related documents that this work is based upon. No changes to those registries are required by this specification.

References Normative References UTF-8, a transformation format of ISO 10646 ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8, the object of this memo. UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. This memo obsoletes and replaces RFC 2279. Uniform Resource Identifier (URI): Generic Syntax A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK] Internet Security Glossary, Version 2 This Glossary provides definitions, abbreviations, and explanations of terminology for information system security. The 334 pages of entries offer recommendations to improve the comprehensibility of written material that is generated in the Internet Standards Process (RFC 2026). The recommendations follow the principles that such writing should (a) use the same term or definition whenever the same concept is mentioned; (b) use terms in their plainest, dictionary sense; (c) use terms that are already well-established in open publications; and (d) avoid terms that either favor a particular vendor or favor a particular technology or mechanism over other, competing techniques that already exist or could be developed. This memo provides information for the Internet community. Augmented BNF for Syntax Specifications: ABNF Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK] 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] The OAuth 2.0 Authorization Framework: Bearer Token Usage This specification describes how to use bearer tokens in HTTP requests to access OAuth 2.0 protected resources. Any party in possession of a bearer token (a "bearer") can use it to get access to the associated resources (without demonstrating possession of a cryptographic key). To prevent misuse, bearer tokens need to be protected from disclosure in storage and in transport. [STANDARDS-TRACK] Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants This specification provides a framework for the use of assertions with OAuth 2.0 in the form of a new client authentication mechanism and a new authorization grant type. Mechanisms are specified for transporting assertions during interactions with a token endpoint; general processing rules are also specified. The intent of this specification is to provide a common framework for OAuth 2.0 to interwork with other identity systems using assertions and to provide alternative client authentication mechanisms. Note that this specification only defines abstract message flows and processing rules. In order to be implementable, companion specifications are necessary to provide the corresponding concrete instantiations. JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants This specification defines the use of a JSON Web Token (JWT) Bearer Token as a means for requesting an OAuth 2.0 access token as well as for client authentication. Guidelines and Registration Procedures for URI Schemes This document updates the guidelines and recommendations, as well as the IANA registration processes, for the definition of Uniform Resource Identifier (URI) schemes. It obsoletes RFC 4395. OAuth 2.0 for Native Apps OAuth 2.0 authorization requests from native apps should only be made through external user-agents, primarily the user's browser. This specification details the security and usability reasons why this is the case and how native apps and authorization servers can implement this best practice. The JavaScript Object Notation (JSON) Data Interchange Format JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data. This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance. The Transport Layer Security (TLS) Protocol Version 1.3 This document specifies version 1.3 of the Transport Layer Security (TLS) protocol. TLS allows client/server applications to communicate over the Internet in a way that is designed to prevent eavesdropping, tampering, and message forgery. This document obsoletes RFC 8446, which specified TLS 1.3. This document obsoletes RFC 5246 (specifying TLS 1.2) and RFCs 5077, 6961, 7627, and 8422, all of which pertain to TLS 1.2 or earlier, and updates RFCs 5705 and 6066. This document also specifies new requirements for TLS 1.2 implementations. HTTP Semantics The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes. This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230. HTTP Caching The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages. This document obsoletes RFC 7234. OAuth 2.0 Authorization Server Issuer Identification This document specifies a new parameter called iss. This parameter is used to explicitly include the issuer identifier of the authorization server in the authorization response of an OAuth authorization flow. The iss parameter serves as an effective countermeasure to "mix-up attacks". Best Current Practice for OAuth 2.0 Security This document describes best current security practice for OAuth 2.0. It updates and extends the threat model and security advice given in RFCs 6749, 6750, and 6819 to incorporate practical experiences gathered since OAuth 2.0 was published and covers new threats relevant due to the broader application of OAuth 2.0. Further, it deprecates some modes of operation that are deemed less secure or even insecure. Deprecating TLS 1.0 and TLS 1.1 This document formally deprecates Transport Layer Security (TLS) versions 1.0 (RFC 2246) and 1.1 (RFC 4346). Accordingly, those documents have been moved to Historic status. These versions lack support for current and recommended cryptographic algorithms and mechanisms, and various government and industry profiles of applications using TLS now mandate avoiding these old TLS versions. TLS version 1.2 became the recommended version for IETF protocols in 2008 (subsequently being obsoleted by TLS version 1.3 in 2018), providing sufficient time to transition away from older versions. Removing support for older versions from implementations reduces the attack surface, reduces opportunity for misconfiguration, and streamlines library and product maintenance. This document also deprecates Datagram TLS (DTLS) version 1.0 (RFC 4347) but not DTLS version 1.2, and there is no DTLS version 1.1. This document updates many RFCs that normatively refer to TLS version 1.0 or TLS version 1.1, as described herein. This document also updates the best practices for TLS usage in RFC 7525; hence, it is part of BCP 195. Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) are used to protect data exchanged over a wide range of application protocols and can also form the basis for secure transport protocols. Over the years, the industry has witnessed several serious attacks on TLS and DTLS, including attacks on the most commonly used cipher suites and their modes of operation. This document provides the latest recommendations for ensuring the security of deployed services that use TLS and DTLS. These recommendations are applicable to the majority of use cases. RFC 7525, an earlier version of the TLS recommendations, was published when the industry was transitioning to TLS 1.2. Years later, this transition is largely complete, and TLS 1.3 is widely available. This document updates the guidance given the new environment and obsoletes RFC 7525. In addition, this document updates RFCs 5288 and 6066 in view of recent attacks. Coded Character Set -- 7-bit American Standard Code for Information Interchange, ANSI X3.4 URL Fetch Standard: CORS protocol Extensible Markup Language Key words for use in RFCs to Indicate Requirement Levels In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. The 'Basic' HTTP Authentication Scheme This document defines the "Basic" Hypertext Transfer Protocol (HTTP) authentication scheme, which transmits credentials as user-id/ password pairs, encoded using Base64. Informative References HTTP State Management Mechanism This document defines the HTTP Cookie and Set-Cookie header fields. These header fields can be used by HTTP servers to store state (called cookies) at HTTP user agents, letting the servers maintain a stateful session over the mostly stateless HTTP protocol. Although cookies have many historical infelicities that degrade their security and privacy, the Cookie and Set-Cookie header fields are widely used on the Internet. This document obsoletes RFC 2965. [STANDARDS-TRACK] OAuth 2.0 Threat Model and Security Considerations This document gives additional security considerations for OAuth, beyond those in the OAuth 2.0 specification, based on a comprehensive threat model for the OAuth 2.0 protocol. This document is not an Internet Standards Track specification; it is published for informational purposes. OAuth 2.0 Token Revocation This document proposes an additional endpoint for OAuth authorization servers, which allows clients to notify the authorization server that a previously obtained refresh or access token is no longer needed. This allows the authorization server to clean up security credentials. A revocation request will invalidate the actual token and, if applicable, other tokens based on the same authorization grant. HTTP Header Field X-Frame-Options To improve the protection of web applications against clickjacking, this document describes the X-Frame-Options HTTP header field, which declares a policy, communicated from the server to the client browser, regarding whether the browser may display the transmitted content in frames that are part of other web pages. JSON Web Token (JWT) JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted. OAuth 2.0 Dynamic Client Registration Protocol This specification defines mechanisms for dynamically registering OAuth 2.0 clients with authorization servers. Registration requests send a set of desired client metadata values to the authorization server. The resulting registration responses return a client identifier to use at the authorization server and the client metadata values registered for the client. The client can then use this registration information to communicate with the authorization server using the OAuth 2.0 protocol. This specification also defines a set of common client metadata fields and values for clients to use during registration. OAuth 2.0 Dynamic Client Registration Management Protocol This specification defines methods for management of OAuth 2.0 dynamic client registrations for use cases in which the properties of a registered client may need to be changed during the lifetime of the client. Not all authorization servers supporting dynamic client registration will support these management methods. Proof Key for Code Exchange by OAuth Public Clients OAuth 2.0 public clients utilizing the Authorization Code Grant are susceptible to the authorization code interception attack. This specification describes the attack as well as a technique to mitigate against the threat through the use of Proof Key for Code Exchange (PKCE, pronounced "pixy"). OAuth 2.0 Token Introspection This specification defines a method for a protected resource to query an OAuth 2.0 authorization server to determine the active state of an OAuth 2.0 token and to determine meta-information about this token. OAuth 2.0 deployments can use this method to convey information about the authorization context of the token from the authorization server to the protected resource. OAuth 2.0 Authorization Server Metadata This specification defines a metadata format that an OAuth 2.0 client can use to obtain the information needed to interact with an OAuth 2.0 authorization server, including its endpoint locations and authorization server capabilities. OAuth 2.0 Device Authorization Grant The OAuth 2.0 device authorization grant is designed for Internet- connected devices that either lack a browser to perform a user-agent- based authorization or are input constrained to the extent that requiring the user to input text in order to authenticate during the authorization flow is impractical. It enables OAuth clients on such devices (like smart TVs, media consoles, digital picture frames, and printers) to obtain user authorization to access protected resources by using a user agent on a separate device. OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens This document describes OAuth client authentication and certificate-bound access and refresh tokens using mutual Transport Layer Security (TLS) authentication with X.509 certificates. OAuth clients are provided a mechanism for authentication to the authorization server using mutual TLS, based on either self-signed certificates or public key infrastructure (PKI). OAuth authorization servers are provided a mechanism for binding access tokens to a client's mutual-TLS certificate, and OAuth protected resources are provided a method for ensuring that such an access token presented to it was issued to the client presenting the token. Resource Indicators for OAuth 2.0 This document specifies an extension to the OAuth 2.0 Authorization Framework defining request parameters that enable a client to explicitly signal to an authorization server about the identity of the protected resource(s) to which it is requesting access. JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens This specification defines a profile for issuing OAuth 2.0 access tokens in JSON Web Token (JWT) format. Authorization servers and resource servers from different vendors can leverage this profile to issue and consume access tokens in an interoperable manner. HTTP/1.1 The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document specifies the HTTP/1.1 message syntax, message parsing, connection management, and related security concerns. This document obsoletes portions of RFC 7230. OAuth 2.0 Pushed Authorization Requests This document defines the pushed authorization request (PAR) endpoint, which allows clients to push the payload of an OAuth 2.0 authorization request to the authorization server via a direct request and provides them with a request URI that is used as reference to the data in a subsequent call to the authorization endpoint. OAuth 2.0 Rich Authorization Requests This document specifies a new parameter authorization_details that is used to carry fine-grained authorization data in OAuth messages. OAuth 2.0 Demonstrating Proof of Possession (DPoP) This document describes a mechanism for sender-constraining OAuth 2.0 tokens via a proof-of-possession mechanism on the application level. This mechanism allows for the detection of replay attacks with access and refresh tokens. OAuth 2.0 Step Up Authentication Challenge Protocol It is not uncommon for resource servers to require different authentication strengths or recentness according to the characteristics of a request. This document introduces a mechanism that resource servers can use to signal to a client that the authentication event associated with the access token of the current request does not meet its authentication requirements and, further, how to meet them. This document also codifies a mechanism for a client to request that an authorization server achieve a specific authentication strength or recentness when processing an authorization request. OAuth 2.0 for Browser-Based Applications This specification details the threats, attack consequences, security considerations, and best practices that must be taken into account when developing browser-based applications that use OAuth 2.0. Encoding claims in the OAuth 2 state parameter using a JWT Yubico YES.com AG ZmartZone IAM This draft provides a method for a client to encode one or more elements encoding information about the session into the OAuth 2 "state" parameter. Updates to OAuth 2.0 JSON Web Token (JWT) Client Authentication and Assertion-Based Authorization Grants Self-Issued Consulting Ping Identity Disney Okta This document updates RFC7521, RFC7522, RFC7523 and RFC9126 with respect to the treatment of audience values in OAuth 2.0 Client Assertion Authentication and Assertion-based Authorization Grants to address a security vulnerability identified in the previous requirements for those audience values in multiple OAuth 2.0 specifications. OAuth 2.0 Attestation-Based Client Authentication MATTR Bundesdruckerei SPRIND This specification defines an extension to the OAuth 2.0 protocol (RFC 6749) that enables a client instance to include a key-bound attestation when interacting with an Authorization Server or Resource Server. This mechanism allows a client instance to prove its authenticity, as verified by a client attester, without revealing its target audience to that attester. It may also serve as a mechanism for client authentication as per OAuth 2.0. OAuth Client ID Metadata Document Okta This specification defines a mechanism through which an OAuth client can identify itself to authorization servers, without prior dynamic client registration or other existing registration. This is through the usage of a URL as a client_id in an OAuth flow, where the URL refers to a document containing the necessary client metadata, enabling the authorization server to fetch the metadata about the client as needed. HTML Living Standard: Cross-document messaging Service Workers OpenID Connect Core 1.0 incorporating errata set 2 OpenID Connect Discovery 1.0 incorporating errata set 2 Online Multimedia Authorization Protocol: An Industry Standard for Authorized Access to Internet Multimedia Resources NIST Special Publication 800-63-1, INFORMATION SECURITY (withdrawn) OWASP Cheat Sheet Series - Unvalidated Redirects and Forwards Content Security Policy Level 2

Augmented Backus-Naur Form (ABNF) Syntax This section provides Augmented Backus-Naur Form (ABNF) syntax descriptions for the elements defined in this specification using the notation of . The ABNF below is defined in terms of Unicode code points ; these characters are typically encoded in UTF-8. Elements are presented in the order first defined. Some of the definitions that follow use the "URI-reference" definition from . Some of the definitions that follow use these common definitions:

"client_id" Syntax The client_id element is defined in :

"client_secret" Syntax The client_secret element is defined in :

"response_type" Syntax The response_type element is defined in and :

"scope" Syntax The scope element is defined in :

"state" Syntax The state element is defined in , , and :

"redirect_uri" Syntax The redirect_uri element is defined in and :

"error" Syntax The error element is defined in , , and :

"error_description" Syntax The error_description element is defined in , , and :

"error_uri" Syntax The error_uri element is defined in , , and :

"grant_type" Syntax The grant_type element is defined in :

"code" Syntax The code element is defined in :

"access_token" Syntax The access_token element is defined in :

"token_type" Syntax The token_type element is defined in and :

"expires_in" Syntax The expires_in element is defined in :

"refresh_token" Syntax The refresh_token element is defined in and :

Endpoint Parameter Syntax The syntax for new endpoint parameters is defined in :

"code_verifier" Syntax The ABNF for code_verifier is as follows.

"code_challenge" Syntax The ABNF for code_challenge is as follows.

Use of application/x-www-form-urlencoded Media Type The application/x-www-form-urlencoded media type is defined by the URL Living Standard , and is registered in the IANA "Media Types" registry with a reference to that definition. When generating content using this media type, names and values MUST be encoded using the UTF-8 character encoding scheme first; the resulting octet sequence is then percent-encoded as defined by the application/x-www-form-urlencoded serializer in . When parsing data from content using this media type, the names and values resulting from reversing the name/value encoding consequently need to be treated as octet sequences, to be decoded using the UTF-8 character encoding scheme. For example, the value consisting of the six Unicode code points (1) U+0020 (SPACE), (2) U+0025 (PERCENT SIGN), (3) U+0026 (AMPERSAND), (4) U+002B (PLUS SIGN), (5) U+00A3 (POUND SIGN), and (6) U+20AC (EURO SIGN) would be encoded into the octet sequence below (using hexadecimal notation): and then represented in the content as:

Serializations Various messages in this specification are serialized using one of the methods described below. This section describes the syntax of these serialization methods; other sections describe when they can and must be used. Note that not all methods can be used for all messages.

Query String Serialization In order to serialize the parameters using the Query String Serialization, the client constructs the string by adding the parameters and values to the query component of a URL using the application/x-www-form-urlencoded format as defined by . Query String Serialization is typically used in HTTP GET requests.

Form-Encoded Serialization Parameters and their values are form-serialized by adding the parameter names and values to the content of the HTTP request using the application/x-www-form-urlencoded format as defined in . Form-Encoded Serialization is typically used in HTTP POST requests.

JSON Serialization The parameters are serialized into a JSON object structure by adding each parameter at the highest structure level. Parameter names and string values are represented as JSON strings. Numerical values are represented as JSON numbers. Boolean values are represented as JSON booleans. Omitted parameters and parameters with no value SHOULD be omitted from the object and not represented by a JSON null value, unless otherwise specified. A parameter MAY have a JSON object or a JSON array as its value. The order of parameters does not matter and can vary.

Extensions The following is a list of extensions that are well established at the time of publication:

: Token Revocation
- The Token Revocation extension defines a mechanism for clients to indicate to the authorization server that an access token is no longer needed.
: Dynamic Client Registration
- Dynamic Client Registration provides a mechanism for programmatically registering clients with an authorization server.
: Token Introspection
- The Token Introspection extension defines a mechanism for resource servers to obtain information about access tokens.
: Authorization Server Metadata
- Authorization Server Metadata (also known as OAuth Discovery) defines an endpoint clients can use to look up the information needed to interact with a particular OAuth server, such as the location of the authorization and token endpoints and the supported grant types.
: OAuth 2.0 Device Authorization Grant
- The Device Authorization Grant (formerly known as the Device Flow) is an extension that enables devices with no browser or limited input capability to obtain an access token. This is commonly used by smart TV apps or devices such as hardware video encoders that can stream video to a streaming video service.
: Mutual TLS
- Mutual TLS describes a mechanism of binding tokens to the clients to which they were issued, as well as a client authentication mechanism, via TLS certificate authentication.
: Resource Indicators
- Resource Indicators provide a way for the client to explicitly signal to the authorization server where it intends to use the access token it is requesting.
: JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens
- This specification defines a profile for issuing OAuth access tokens in JSON Web Token (JWT) format.
: Pushed Authorization Requests
- The Pushed Authorization Requests extension describes a technique of initiating an OAuth flow from the back channel, providing better security and more flexibility for building complex authorization requests.
: Authorization Server Issuer Identification
- The iss parameter in the authorization response indicates the identity of the authorization server to prevent mix-up attacks in the client.
: Rich Authorization Requests
- Rich Authorization Requests specifies a new parameter authorization_details that is used to carry fine-grained authorization data in the OAuth authorization request.
: Demonstrating Proof of Possession (DPoP)
- DPoP describes a mechanism for sender-constraining OAuth 2.0 tokens via a proof-of-possession mechanism at the application level.
: Step-Up Authentication Challenge Protocol
- Step-Up Auth describes a mechanism that resource servers can use to signal to a client that the authentication event associated with the access token of the current request does not meet its authentication requirements.

Acknowledgements This specification is the work of the OAuth Working Group, and its starting point was based on the contents of the following specifications: OAuth 2.0 Authorization Framework (RFC 6749), OAuth 2.0 for Native Apps (RFC 8252), OAuth Security Best Current Practice, and OAuth 2.0 for Browser-Based Applications. The editors would like to thank everyone involved in the creation of those specifications upon which this is built. The editors would also like to thank the following individuals for their ideas, feedback, corrections, and wording that helped shape this version of the specification: Andrii Deinega, Bob Hamburg, Brian Campbell, Brian Pontarelli, Brock Allen, Daniel Fett, Deng Chao, Emelia Smith, Falko, Filip Skokan, Frederik Krogsdal Jacobsen, George Fletcher, Goutam Adwant, Jeremy Tennant, Johannes Koch, Joseph Heenan, Justin Richer, Karsten Meyer zu Selhausen, Lauritz Holtmann, Max Gerber, Michael Jones, Michael Peck, Nick Watson, Roberto Polli, Shon T. Urbas, Tim Würtele, and Vittorio Bertocci. Discussions around this specification have also occurred at the OAuth Security Workshop in 2021 and 2022. The authors thank the organizers of the workshop (Guido Schmitz, Steinar Noem, and Daniel Fett) for hosting an event that's conducive to collaboration and community input.

Document History -17

Added obsoletes: 6749, 6750 to the document metadata
Added access_token to the parameters called out in Injection and Input Validation
Changed "MAY" to "may" in the client impersonation subsections, since they describe inputs to a decision made only by the authorization server
Updated the application/x-www-form-urlencoded appendix to reference the WHATWG URL Standard and its IANA registration, and used "URL" consistently for the authorization endpoint and authorization request
Clarified that the client impersonation mitigation requires active resource owner interaction rather than explicit re-authentication
Added examples of authorization server policies for issuing refresh tokens
Editorial alignment with the HTTP WG style guide: named references for HTTP, HTTP caching, HTTP/1.1, TLS, and cookies; status code, field, and method formatting; quoted registry names; HTTP examples labeled as http-message and wrapped per RFC 8792
Clarified that an authorization server supporting both OAuth 2.0 and OAuth 2.1 clients determines which rules apply to each client through its configuration for that client
Removed duplicate "Access Token Privilege Restriction" section
Clarified that redirect URI comparison is case-sensitive and aligned loopback redirect URI terminology
Clarified that claimed https scheme redirects do not authenticate the client
Restored loopback interception note from RFC 8252
Updated attribution of the token threat list to NIST SP 800-63-1
Clarified scope of grants and refresh token requests when the resource owner revokes scopes
Added note about refresh token rotation and lost responses
Updated abstract protocol flow diagram and description to show the authorization server as the intermediary for the authorization request
Filled in the Browser-Based Applications section with the normative requirements from RFC 10017
Updated references to OAuth 2.0 for Browser-Based Applications to the published RFC 10017
Made auth-param values optional in the WWW-Authenticate Bearer challenge
Clarified WWW-Authenticate behavior for client authentication methods that do not use an HTTP authentication scheme
Clarified that the query component of the redirect URI and authorization endpoint must not include parameters defined for the request or response
Clarified serialization of authorization request parameters when using GET or POST
Added note about interoperability with OAuth 2.0 clients
Clarified that the privileges in an access token are not necessarily the only factor in a resource server's access control decision
Added a reference to RFC 10017 for considerations on choosing a CORS policy
Simplified mix-up defense via issuer identification to rely on the required iss response parameter
Mentioned state alongside the authorization code in the Value Sizes section
Replaced obsolete and superseded references
Editorial cleanups

-16

Remove PKCE plain method
Mention PAR in the authorization endpoint definition section
Added security consideration section about OAuth consent phishing
Make iss response parameter required to be sent by the AS (let clients choose the mix-up mitigation still)
Consolidated text about lengths of values into a new "Value Sizes" section
Clarified authorization endpoint error response behavior

-15

add additional context for JWT client authentication and specifically recommend RFC7523bis
editorial clarifications and updates
clarify error responses in authorization endpoint and token endpoint
synced language from RFC9700 for AS open redirect considerations
applied RFC6750 erratas 3500 and 6613
resolved ambiguity around repeated parameters

-14

Editorial clarifications
Corrected an instance of "relying party" vs "resource server"
Add references to client_secret_post and client_secret_basic terms from RFC7591
Replaced "sanitize" language with treating as untrusted input
Clarified that native apps guidance applies primarily to mobile app platforms
Clarify that there is no requirement that an AS supports public or confidential clients in particular

-13

Updated references to RFC 9700
Updated and sorted list of OAuth extensions
Updated references to link to section numbers

-12

Updated language around client registration to better reflect alternative registration methods such as those in use by OpenID Federation and open ecosystems
Added DPoP and Step-Up Auth to appendix of extensions
Updated reference for case insensitivity of auth scheme to HTTP instead of ABNF
Corrected an instance of "relying party" vs "client"
Moved client_id requirement to the individual grant types
Consolidated the descriptions of serialization methods to the appendix

-11

Explicitly mention that Bearer is case insensitive
Recommend against defining custom scopes that conflict with known scopes
Change client credentials to be required to be supported in the request body to avoid HTTP Basic authentication encoding interop issues

-10

Clarify that the client id is an opaque string
Extensions may define additional error codes on a resource request
Improved formatting for error field definitions
Moved and expanded "scope" definition to introduction section
Split access token section into structure and request
Renamed b64token to token68 for consistency with RFC7235
Restored content from old appendix B about application/x-www-form-urlencoded
Clarified that clients must not parse access tokens
Expanded text around when redirect_uri parameter is required in the authorization request
Changed "permissions" to "privileges" in refresh token section for consistency
Consolidated authorization code flow security considerations
Clarified authorization code reuse - an authorization code can only obtain an access token once

-09

AS MUST NOT support CORS requests at authorization endpoint
more detail on asymmetric client authentication
sync CSRF description from security BCP
update and move sender-constrained access tokens section
sync client impersonating resource owner with security BCP
add reference to authorization request from redirect URI registration section
sync refresh rotation section from security BCP
sync redirect URI matching text from security BCP
updated references to RAR (RFC9396)
clarifications on URIs
removed redirect_uri from the token request
expanded security considerations around code_verifier
revised introduction section

-08

Updated acknowledgments
Swap "by a trusted party" with "by an outside party" in client ID definition
Replaced "verify the identity of the resource owner" with "authenticate"
Clarified refresh token rotation to match RFC6819
Added appendix to hold application/x-www-form-urlencoded examples
Fixed references to entries in appendix
Incorporated new "Phishing via AS" section from Security BCP
Rephrase description of the motivation for client authentication
Moved "scope" parameter in token request into specific grant types to match OAuth 2.0
Updated Clickjacking and Open Redirection description from the latest version of the Security BCP
Moved normative requirements out of authorization code security considerations section
Security considerations clarifications, and removed a duplicate section

-07

Removed "third party" from abstract
Added MFA and passwordless as additional motiviations in introduction
Mention PAR as one way redirect URI registration can happen
Added a reference to requiring CORS headers on the token endpoint
Updated reference to OMAP extension
Fixed numbering in sequence diagram

-06

Removed "credentialed client" term
Simplified definition of "confidential" and "public" clients
Incorporated the iss response parameter referencing RFC9207
Added section on access token validation by the RS
Removed requirement for authorization servers to support all 3 redirect methods for native apps
Fixes for some references
Updates HTTP references to RFC 9110
Clarifies "authorization grant" term
Clarifies client credential grant usage
Clean up authorization code diagram
Updated reference for application/x-www-form-urlencoded and removed outdated note about it not being in the IANA registry

-05

Added a section about the removal of the implicit flow
Moved many normative requirements from security considerations into the appropriate inline sections
Reorganized and consolidated TLS language
Require TLS on redirect URIs except for localhost/custom URL scheme
Updated refresh token guidance to match security BCP

-04

Added explicit mention of not sending access tokens in URI query strings
Clarifications on definition of client types
Consolidated text around loopback vs localhost
Editorial clarifications throughout the document

-03

refactoring to collect all the grant types under the same top-level header in section 4
Better split normative and security consideration text into the appropriate places, both moving text that was really security considerations out of the main part of the document, as well as pulling normative requirements from the security considerations sections into the appropriate part of the main document
Incorporated many of the published errata on RFC6749
Updated references to various RFCs
Editorial clarifications throughout the document

-02 -01 -00

initial revision