Draft
Add "none" to token_endpoint_auth_methods_supported when CIMD feature is enabled#1102
Conversation
… is enabled Fixes keycloak#49730 When the CIMD feature is enabled, MCP clients require both "client_id_metadata_document_supported": true and "none" in token_endpoint_auth_methods_supported to select CIMD over DCR. This change adds "none" to the supported auth methods list when CIMD is enabled.
Copilot created this pull request from a session on behalf of
tnorimat
June 7, 2026 13:19
View session
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
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.
When
--features=cimdis enabled, the discovery document advertisesclient_id_metadata_document_supported: truebut omits"none"fromtoken_endpoint_auth_methods_supported. MCP clients (e.g. Claude) require both fields to select CIMD over Dynamic Client Registration per the MCP specification.Description
OIDCWellKnownProvider: add"none"to the token endpoint auth methods list when the CIMD feature is enabledClientIdMetadataDocumentTest: add test verifying bothclient_id_metadata_document_supportedand"none"intoken_endpoint_auth_methods_supportedare present when CIMD is activeAfter fix: