RFC 8693: OAuth 2.0 Token Exchange
In plain English — editorial summary, not part of the RFC
This specification defines a protocol for an HTTP- and JSON-based Security Token Service (STS) by defining how to request and obtain security tokens from OAuth 2.0 authorization servers, including security tokens employing impersonation and delegation.
Document record
- Document ID
- RFC8693
- Published
- January 2020
- Authors
- M. Jones; A. Nadalin; B. Campbell; J. Bradley; C. Mortimore
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 27
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8705OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access TokensCurrent
February 2020
- RFC 8417Security Event Token (SET)Current
July 2018
- RFC 8414OAuth 2.0 Authorization Server MetadataCurrent
June 2018
- RFC 8392CBOR Web Token (CWT)Current
May 2018
- RFC 9101The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)Current
August 2021
- RFC 9728OAuth 2.0 Protected Resource MetadataCurrent
April 2025
- RFC 7523JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization GrantsCurrent
May 2015
- RFC 8725JSON Web Token Best Current PracticesCurrent
February 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?