[Identity] Update tenant resolution logic #42721
Draft
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
Our tenant resolution logic shouldn't error out requests for certain dev credentials (e.g. `DeviceCodeCredential and `InteractiveBrowserCredential`) if a tenant is passed into `get_token` or `get_token_info`. This happens if the no tenant was configured on the credential and the default "organizations" tenant is used. Signed-off-by: Paul Van Eck <[email protected]>
github-project-automation
bot
moved this to Untriaged
in Azure Identity SDK Improvements
Signed-off-by: Paul Van Eck <[email protected]>
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
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.
Our tenant resolution logic shouldn't error out requests for certain dev credentials (e.g.
DeviceCodeCredentialandInteractiveBrowserCredential) if a tenant is passed intoget_tokenorget_token_info. This happens if the no tenant was configured on the credential and the default "organizations" tenant is used.