Repository navigation
Conversation
…stration The conformance client registers itself through Dynamic Client Registration without application_type, which SEP-837 requires, so ten auth scenarios in the 2026-07-28 client suite fail. Register as "native", since the client runs locally and redirects to a loopback URL. fixes modelcontextprotocol#801
This branch has not been deployed
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.
Specify
application_type: "native"when the conformance client registers itself through Dynamic Client Registration.fixes #801
Motivation and Context
SEP-837, part of the 2026-07-28 spec, requires clients to specify an appropriate
application_typeduring Dynamic Client Registration (Application Type and Redirect URI Constraints). Without it, OpenID Connect servers treat the client asweband may reject itshttp://localhostredirect URI.The conformance client is a local command-line program that always redirects to the loopback URL
http://localhost:3000/callback(CALLBACK_URL). The spec lists such clients as native applications, so it always registers as"native".In the 2026-07-28 client suite, ten auth scenarios that register the client this way failed only on
sep-837-application-type-present. With this change they pass. #1069 asks CI to require these suites to pass at 100%.How Has This Been Tested?
CI runs conformance 0.1.16, which does not include the 2026-07-28 suites, so I ran the client suites locally with 0.2.0-alpha.12:
The auth suite of 0.1.16, which CI runs, also passes, and so does
./gradlew :conformance-test:ktlintCheck.Breaking Changes
None. Only the conformance client changes.
Types of changes
Checklist
Additional context
The conformance client is the only code in
mainthat registers a client, so this covers SEP-837 for the repository as it is today.