Add client_id_metadata_document_supported to OAuthMetadata #1603
+1
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add support for the client_id_metadata_document_supported field as specified in draft-parecki-oauth-client-id-metadata-document-00. This boolean field indicates whether the authorization server supports retrieving client metadata from a client_id URL.
pcarleton
approved these changes
Nov 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for the
client_id_metadata_document_supportedfield to theOAuthMetadataclass as specified in draft-parecki-oauth-client-id-metadata-document-00.Motivation and Context
This field is part of the OAuth Client ID Metadata Document specification. It allows authorization servers to indicate whether they support retrieving client metadata from a
client_idURL. This enables clients to determine server capabilities before redirecting users, preventing errors about invalid clients.How Has This Been Tested?
The change has been verified with:
Breaking Changes
None. This is an additive change that adds an optional field to the
OAuthMetadatamodel.Types of changes
Checklist
Additional context
This implements the authorization server metadata field specified in Section 5 of the draft specification. The field is registered in the IANA "OAuth Authorization Server Metadata" registry established by RFC 8414.