Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to clear credential in client side in Azure Machine Learning extension in VS code? #2447

Closed
zyeric opened this issue Sep 6, 2024 · 2 comments
Assignees
Labels
accessibility Issues related to accessibility fixes. triage-needed

Comments

@zyeric
Copy link

zyeric commented Sep 6, 2024

Expected Behavior

I have two azure accounts A and B, both of them have been used to logged my personal computer.

My azure compute instance is submitted by A.

When I try to access the instance by VS code + Azure machine learning toolkit, my credential was set to B by mistake. As a result, it failed to connect to the instance.

How can I clear the credential in my local device so that I can connect to the resource by B correctly?

Actual Behavior

There is no chance to re-select the credential during the connection process. And the error message is

User B cannot connect to the interactive job xxx as it was submitted by A. Please sign in to the correct account or connect to a job submitted by B.

Steps to Reproduce the Problem

NA

Specifications

  • Version: azure machine learning v1.0.0, vscode 1.93.0
  • Platform: windows 11
  • Screen Reader:
@zyeric zyeric added the accessibility Issues related to accessibility fixes. label Sep 6, 2024
@tbombach
Copy link
Member

Hi @zyeric, I apologize for the issue you are encountering. Do you see account B in the Accounts section (n the bottom left of the VS Code window? If so, could you sign out of that account and sign in with account A?

@zyeric
Copy link
Author

zyeric commented Sep 24, 2024

@tbombach thanks for your reply. I tried to clear all extensions cache (%USERPROFILE%/.vscode/extensions) and all settings (%APPDATA%\Code) and it works (although need to reinstall extensions).
I will try your approach next time I encounter the problem.

@zyeric zyeric closed this as completed Sep 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Issues related to accessibility fixes. triage-needed
Projects
None yet
Development

No branches or pull requests

2 participants