The OAuth 2.0 Authorization Framework: Bearer Token Usage

Metadata

Publisher: IETF
Doc Type: Standard
Pages: 18
Abstract: 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]
Publication Date: 2012-10-01
Status Note: Proposed Standard
DOI: 10.17487/RFC6750
Link: https://doi.org/10.17487/RFC6750
Author(s): Michael B. Jones
Dick Hardt
Keyword(s): Resource Owner, Resource Server, Protected Resource, Refresh Token, Access Token Scope, Bearer Authorization Header, Bearer Access Token Type

Latest version of IETF RFC 6750

Document Versions — IETF RFC 6750

▶ IETF RFC 6750 (2012-10-01)

THIS DOC [ACTIVE] [LATEST VERSION]

Amended by:

IETF RFC 8996 [Active*]
RFC9700 NOT IN REGISTRY

Normative Reference(s)

ANSI/INCITS X3.4:1986 (R1997) [Active]
IETF RFC 2119 [Active*]
IETF RFC 2246 [Superseded*]
IETF RFC 2616 [Superseded*]
IETF RFC 2617 [Superseded*]
IETF RFC 2818 [Superseded*]
IETF RFC 3986 [Active, Amended*]
IETF RFC 5234 [Active, Amended*]
IETF RFC 5246 [Superseded*]
IETF RFC 5280 [Active, Amended*]
IETF RFC 6265 [Active*]
IETF RFC 6749 [Active*]
W3C.html401.19991224 — [HTML-4.01] REC-html401-19991224, W3C Recommendation: HTML 4.01 Specification (December 24 th , 1999). EXTERNAL
W3C.webarch.20041215 — REC-webarch EXTERNAL

Bibliographic Reference(s)

NIST.SP.800-63-1 — NIST800-63 EXTERNAL
Sakimura, N., Bradley, J., Jones, M., de Medeiros, B., Mortimore, C., and E. Jay, "OpenID Connect Messages 1.0", June 2012, < http://openid.net/specs/ openid-connect-messages-1_0.html >. EXTERNAL
Huff, J., Schlacht, D., Nadalin, A., Simmons, J., Rosenberg, P., Madsen, P., Ace, T., Rickelton-Abdi, C., and B. Boyer, "Online Multimedia Authorization Protocol: An Industry Standard for Authorized Access to Internet Multimedia Resources", April 2012, < http://www.oatc.us/Standards/Download.aspx >. EXTERNAL
Fielding, R., Ed., and J. Reschke, Ed., "Hypertext Transfer Protocol (HTTP/1.1): Authentication", Work in Progress, October 2012. EXTERNAL

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC6750.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree

Reference this Doc

Plain text (ISO 690 compliant)

Preview:

IETF RFC 6750, The OAuth 2.0 Authorization Framework: Bearer Token Usage. Available at https://doi.org/10.17487/RFC6750

Snippet:

IETF RFC 6750, The OAuth 2.0 Authorization Framework: Bearer Token Usage. Available at https://doi.org/10.17487/RFC6750

HTML (ISO 690 compliant)

Preview:

IETF RFC 6750, The OAuth 2.0 Authorization Framework: Bearer Token Usage. Available at https://doi.org/10.17487/RFC6750

Snippet:

<span class="citation"><cite>IETF RFC 6750</cite>, The OAuth 2.0 Authorization Framework: Bearer Token Usage. Available at <a href="https://doi.org/10.17487/RFC6750" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6750</a></span>

SMPTE's HTML Pub

Preview:

IETF RFC 6750, The OAuth 2.0 Authorization Framework: Bearer Token Usage
doi: 10.17487/RFC6750
url: https://doi.org/10.17487/RFC6750

Snippet:

<li>
<cite id="bib-rfc6750">IETF RFC 6750</cite>, The OAuth 2.0 Authorization Framework: Bearer Token Usage
<span class="doi">10.17487/RFC6750</span>
</li>

Referenced By

Technology Components for a Data-Driven Personalized Media Experience in Broadcasting [Active]
IETF RFC 6749 [Active*]
IETF RFC 8996 [Active*]
IETF RFC 9725 [Active*]