BearerTokenChallengeAuthorizationPolicy extracting tenant ID #44280
Conversation
This file contains 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
ibrahimrabab
requested review from
seanmcc-msft,
ibrandes,
kyleknap and
alzimmermsft
as code owners
g2vinay
reviewed
Feb 20, 2025
| if (scope != null) { | ||
| String authorization = challenges.get("authorization_uri"); | ||
|
|
||
| if (scope != null && authorization != null) { |
There was a problem hiding this comment.
authorization check should be in separate independent if block and then parse the tenant ID.
While its not common but its possible that authorization_uri is not present but scope/resource id is, need to accomodate this scenario.
|
API change check API changes are not detected in this pull request. |
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.
Description
resolves #44167