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

Feature Request: Add support for DeviceCode #7644

Closed
3 tasks done
cdiskan opened this issue Jan 5, 2024 · 2 comments
Closed
3 tasks done

Feature Request: Add support for DeviceCode #7644

cdiskan opened this issue Jan 5, 2024 · 2 comments
Labels
✅ mitigated Has been resolved or has known workaround

Comments

@cdiskan
Copy link

cdiskan commented Jan 5, 2024

Preflight Checklist

Problem

Azure storage explorer requires a browser on the device in order to sign in.

Desired Solution

Support az login --use-device-code or other similar method to authenticate Azure storage explorer by using a web browser on a separate device

Alternatives and Workarounds

Currently utilizing connection strings and keys for individual storage accounts. However, this does not scale well as we have hundreds of storage accounts. Additionally, doing so negativley impacts logging, as actions taken under SAS are not uniquely attributable to a user for legal\auditing purposes.

Additional Context

In highly regulated environments, use of web browsers is significantly limited. When migrating large amounts of data, Azure storage explorer is most effectively run on well-connected high availability systems. However, these devices are also the least likely to be able to run a web browser. (Either from a technical or regulatory limitation). To address this issue, Azure storage explorer should allow sign-in via device code in the same manner that Azure CLI on powershell does. This would eliminate the dependency on having a browser that can reach the internet installed on the storage server(s) that Storage Explorer is installed on. Additionally it would allow storage explorer to login when used as a Remote App (Via Remote Desktop Services) which currently does not function because the storage explorer login process takes place in a different process\application than is being broadcast via remote desktop services.

@JasonYeMSFT
Copy link
Contributor

JasonYeMSFT commented Jan 8, 2024

Could you try go to Settings > Application > Sign In With and change it to "Device Code Flow" and then retry sign-in? I believe it can achieve what you want.

@MRayermannMSFT
Copy link
Member

As @JasonYeMSFT says, this is already implemented. See here for instructions.
https://learn.microsoft.com/en-us/azure/storage/common/storage-explorer-sign-in#changing-where-sign-in-happens

@MRayermannMSFT MRayermannMSFT added the ✅ mitigated Has been resolved or has known workaround label Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✅ mitigated Has been resolved or has known workaround
Projects
None yet
Development

No branches or pull requests

3 participants