Visual RFC.
ALL RFCs / RFC 6750
Read the RFC ↗
RFC 6750 / MECHANISMS

Possession is the credential

01

A bearer token can be used by any party possessing it, without proving possession of a cryptographic key.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 1.2 ↗
RFC 6750 · § 1.2EXAMPLE
3 / 3
Possession is the credentialA bearer token can be used by any party possessing it, without proving possession of a cryptographic key. Current state: Bearer replay.Possession is the credentialClientbearer TOKENResourceToken copiedreplay TOKENBearer possession requires no proof of a bound private key.
03
Bearer replay

Possession alone can let the thief act within the token’s privileges.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 6750 bearer possessionRFC 9700 § 2.2

The OAuth security BCP recommends sender-constraining access tokens to reduce the consequences of replaying a stolen token.

Read the updated RFC section ↗
KEY POINT

Protect bearer tokens from disclosure in storage and transit.

  • Protect bearer tokens from disclosure in storage and transit.
  • A copied token may be replayed by its possessor.
  • Sender-constrained tokens add a different proof requirement.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Possession is the credential
  2. Put it in the request header
  3. URLs leave extra copies
  4. Errors describe different failures
  5. Limit the damage of disclosure
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗