Skip to content

docs(ENG-4143): say sign-in takes a client ID metadata document as well as dynamic registration - #9

Merged
glebedel merged 1 commit into
mainfrom
guillaume/eng-4143-plugin-auth-docs
Nov 13, 2026
Merged

glebedel merged 1 commit into
mainfrom
guillaume/eng-4143-plugin-auth-docs

Conversation

@glebedel

@glebedel glebedel commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

The README and the .mcp.json note say sign-in uses dynamic client registration. Since auth#760 (turned on in prod by auth#780), idp-api.stackone.com also 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:

GET https://idp-api.stackone.com/.well-known/oauth-authorization-server/api/auth
{"issuer":"https://idp-api.stackone.com/api/auth",
 "registration_endpoint":"https://idp-api.stackone.com/api/auth/oauth2/register",
 "client_id_metadata_document_supported":true,
 "token_endpoint_auth_methods_supported":["none","client_secret_basic","client_secret_post","private_key_jwt"]}

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.

Gate Result
Forge, security scan, Codex security, /security-review not run: docs-only (README prose and a JSON note string)
Demo no runtime change, no demo
JSON .mcp.json parses; no em or en dashes

Not changed here, worth a look: validate.yml asserts registration_endpoint is 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.json to mention that idp-api.stackone.com now 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.

View guided diff Turn on auto-fix

…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>
@glebedel glebedel self-assigned this Nov 12, 2026
@glebedel
glebedel merged commit 9c95a3f into main Nov 13, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants