Skip to content

Correct default VisualStudioCodeCredential environment name#14648

Merged
chlowell merged 2 commits intoAzure:masterfrom
chlowell:vscode-default-environment
Nov 4, 2020
Merged

Correct default VisualStudioCodeCredential environment name#14648
chlowell merged 2 commits intoAzure:masterfrom
chlowell:vscode-default-environment

Conversation

@chlowell
Copy link
Copy Markdown
Member

Closes #14438, the gist of which is that VS Code Azure Account extension doesn't purge the refresh token it stores as its "Azure" token when the user signs out. Currently, VisualStudioCodeCredential will use this token when it finds no more specific cloud identified in VS Code's settings file (as it would if a user were signed in to the extension). Thus the credential can attempt to redeem an expired refresh token, and raise ClientAuthenticationError rather than the CredentialUnavailableError we want when no user is signed in to the extension.

This implements the fix proposed in #14438, changing the default environment to "AzureCloud", which the extension does purge when the user signs out, and uses as its own default environment.

@chlowell chlowell added Client This issue points to a problem in the data-plane of the library. Azure.Identity labels Oct 20, 2020
@chlowell chlowell requested a review from g2vinay October 20, 2020 23:38
with open(path) as file:
data = json.load(file)
environment_name = data.get("azure.cloud", "Azure")
environment_name = data.get("azure.cloud", "AzureCloud")
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The change looks fine.
Shouldn't this env also alter the target Azure Auth Host for VS code client ?
the auth host provided via kwargs/constructor/env will take priority, but if isn't specified then this env should be used to target a specific auth host too.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps; that would be a new feature. I put it on the backlog as #14808

g2vinay
g2vinay previously approved these changes Oct 29, 2020
@chlowell chlowell merged commit aebd212 into Azure:master Nov 4, 2020
@chlowell chlowell deleted the vscode-default-environment branch November 4, 2020 17:44
openapi-sdkautomation Bot pushed a commit to AzureSDKAutomation/azure-sdk-for-python that referenced this pull request Jun 9, 2021
Move swagger from private repo to public repo (Azure#14648)

* Adding Swagger for AzureData on AzureArc

* rename folder to AzureArcData

* Adding Operations

* Revert "Adding Operations". Keeping it the same with old approved
swagger

This reverts commit 83ff5548c0d605829d656a461a416e517fa8b49e.

* Bump version to 2020-12-08

* Move 2021-06-01-preview to public repo

* Fixing SDK generation

Co-authored-by: Shuo Li <shul@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Azure.Identity Client This issue points to a problem in the data-plane of the library.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] VsCode Credential not reading correct values from the access token cache.

3 participants