docs: complete account linking guidance in enterprise-managed authori…#2960
Open
karankraina wants to merge 2 commits into
Open
docs: complete account linking guidance in enterprise-managed authori…#2960karankraina wants to merge 2 commits into
karankraina wants to merge 2 commits into
Conversation
Author
|
Hey @CaitieM20 Would love to have your review on this |
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
1 participant
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.
Complete the incomplete sentence in the "For MCP Authorization Servers" section regarding account linking with ID-JAG token claims.
Motivation and Context
The enterprise-managed authorization documentation had an incomplete bullet point (point 3 under "For MCP Authorization Servers") that cut off mid-sentence. This left implementers without guidance on how to handle account linking using subject and email claims from ID-JAG tokens.
How Has This Been Tested?
Documentation-only change. Verified the rendered content reads correctly and provides actionable guidance for MCP Authorization Server implementers.
Breaking Changes
None
Types of changes
Checklist
Additional context
The completed sentence advises implementers to use the subject claim as the primary stable identifier and fall back to the email claim for matching pre-existing accounts created before enterprise-managed authorization was configured.