Repository navigation
docs(ENG-4143): say sign-in takes a client ID metadata document as well as dynamic registration - #9
Merged
Conversation
…ll as dynamic registration idp-api.stackone.com now advertises client_id_metadata_document_supported (auth#760, enabled in prod by auth#780) next to its registration endpoint, so hosts that support URL-based client IDs sign in without registering. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Guillaume Lebedel <10488548+glebedel@users.noreply.github.com>
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.
The README and the
.mcp.jsonnote say sign-in uses dynamic client registration. Since auth#760 (turned on in prod by auth#780),idp-api.stackone.comalso accepts a client ID metadata document (URL-based client ID, MCP SEP-991), so a host that supports it signs in without registering a client. This PR updates the two places that describe the sign-in. No change to the server URL, manifests or versions.Live metadata, fetched 2026-11-12:
Context: raised while fixing ENG-4143 (StackOne as an MCP client could not connect to Luma, whose auth server offers only CIMD): StackOneHQ/unified-cloud-api#9678. That fix needs nothing from this plugin, which is a client of StackOne's own server.
/security-reviewnotestring).mcp.jsonparses; no em or en dashesNot changed here, worth a look:
validate.ymlassertsregistration_endpointis present ("no DCR"). That passes today, but it would fail the day auth drops DCR in favour of CIMD (MCP 2026-07-28 deprecates DCR). Workflow files cannot be pushed by the s2d2 App, so that edit is left for a person.Requested by guillaume@stackone.com in Slack (#C094LSQ6BNV thread 1794477428.490329).
🤖 Generated with Claude Code
Summary by cubic
Updates the sign-in documentation in the README and
.mcp.jsonto mention thatidp-api.stackone.comnow accepts a client ID metadata document (CIMD) in addition to dynamic client registration. The docs previously described only dynamic registration, so hosts that support URL-based client IDs can now sign in without registering a client. Docs-only change: the server URL, manifests, and versions are unchanged.Written for commit 90f3ca3. Summary will update on new commits.