Fix Azure scope validation #2269
Merged
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.
Azure returns unprefixed scopes in JWT tokens (e.g.,
'scp': 'read') but requires prefixed scopes in authorization requests (e.g.,'scope': 'api://xxx/read'). The previous implementation validated tokens against prefixed scopes, causing MCP clients to reject tokens with "invalid_token" errors.Simplified
AzureProviderto use standardJWTVerifierwith unprefixed scopes. Scopes are only prefixed when building Azure's authorization URL via the_build_upstream_authorize_url()override.Closes #2263