Bugfix: DefaultAzureCredential
/IntelliJCredential
doesn't work even when the user is already signed in to Azure Plugin for IntelliJ.
#37927
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
This PR fixes the problem that
DefaultAzureCredential
/IntelliJCredential
doesn't work even when the user is already signed in to newer versions of the Azure Plugin for IntelliJ.#35419, #27307, ...
Why it doesn't work with newer versions of Azure Plugin for IntelliJ
IntelliJCredential
reads theAuthMethodDetails.json
file generated by old versions of the Azure Plugin for IntelliJ. However, newer versions no longer generate this file.Why this fix works
The newer versions of the Azure Plugin for IntelliJ implement authentication using
azure-identity
and recover the sign-in status across startups by leveraging the persistent token cache.This fix tries to authenticate with the persisted token cache by the Azure Plugin for IntelliJ first and then uses
authenticateWithIntelliJ
(for backward compatibility).All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines