RFC 8414: OAuth 2.0 Authorization Server Metadata
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8414
- Published
- June 2018
- Authors
- M. Jones; N. Sakimura; J. Bradley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9728OAuth 2.0 Protected Resource MetadataCurrent
April 2025
- RFC 9101The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)Current
August 2021
- RFC 8935Push-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8936Poll-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 7519JSON Web Token (JWT)Updated
May 2015
- RFC 8417Security Event Token (SET)Current
July 2018
- RFC 8392CBOR Web Token (CWT)Current
May 2018
- RFC 8693OAuth 2.0 Token ExchangeCurrent
January 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?