fix: OAuth login authority for MSA-based orgs #591
Merged
Conversation
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
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
aaudzei
force-pushed
the
users/antonaudzei/587
branch
from
41d152a to
b9a5690
Compare
danhellem
approved these changes
Oct 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
OAuth login requires special treatment for ADO orgs that are not hosted under MS tenants.
The mapping for such orgs resolves tenant value as zero GUID
00000000-0000-0000-0000-000000000000.And such orgs require "common" authority for issuing the auth token.
GitHub issue number
#587
Associated Risks
None
✅ PR Checklist
🧪 How did you test it?
E2E using VSCode as MCP Client