The existing OAuth 2.0 Authorization Server Metadata specification has now been joined by a related OAuth 2.0 Protected Resource Metadata specification. This means that JSON metadata formats are now defined for all the OAuth 2.0 parties: clients, authorization servers, and protected resources.
The most significant addition to the OAuth 2.0 Authorization Server Metadata specification is enabling signed metadata, represented as claims in a JSON Web Token (JWT). This is analogous to the role that the Software Statement plays in OAuth Dynamic Client Registration. Signed metadata can also be used for protected resource metadata.
For use cases in which the set of protected resources used with an authorization server are enumerable, the authorization server metadata specification now defines the “
protected_resources” metadata value to list them. Likewise, the protected resource metadata specification defines an “
authorization_servers” metadata value to list the authorization servers that can be used with a protected resource, for use cases in which those are enumerable.
The specifications are available at:
HTML-formatted versions are also available at: