RFC 8414: 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…

Read RFC 8414 on the RFC Editor

Incoming relationships (14 related RFCs)

Normatively referenced by — RFC 8705: OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens
Normatively referenced by — RFC 9068: JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens
Normatively referenced by — RFC 9126: OAuth 2.0 Pushed Authorization Requests
Normatively referenced by — RFC 9396: OAuth 2.0 Rich Authorization Requests
Normatively referenced by — RFC 9700: Best Current Practice for OAuth 2.0 Security
Normatively referenced by — RFC 9701: JSON Web Token (JWT) Response for OAuth Token Introspection
Normatively referenced by — RFC 9728: OAuth 2.0 Protected Resource Metadata
Informatively referenced by — RFC 8725: JSON Web Token Best Current Practices
Informatively referenced by — RFC 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
Informatively referenced by — RFC 9449: OAuth 2.0 Demonstrating Proof of Possession (DPoP)
Informatively referenced by — RFC 9470: OAuth 2.0 Step Up Authentication Challenge Protocol
Informatively referenced by — RFC 9560: Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect
Informatively referenced by — RFC 8898: Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)
Informatively referenced by — RFC 9864: Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)