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

Authenticate to storage account using Azure credentials rather than SAS key? #3927

Open
jonnyry opened this issue May 9, 2024 · 4 comments
Labels
question Further information is requested

Comments

@jonnyry
Copy link
Collaborator

jonnyry commented May 9, 2024

Using Storage Explorer running on a VM within the TRE, is it possible (/should it be possible) to connect to a storage account (such as the workspace's storage account) using Azure Entra ID credentials, rather than using SAS keys?

@jonnyry jonnyry added the question Further information is requested label May 9, 2024
@jonnyry jonnyry changed the title Authenticate to storage account using Azure username rather than SAS key? Authenticate to storage account using Azure credentials rather than SAS key? May 9, 2024
@tim-p-allen
Copy link
Collaborator

It isn't possible currently, this issue here #1148 could help if this was to become a feature.

@jonnyry
Copy link
Collaborator Author

jonnyry commented May 9, 2024

Ah, I'm not suggesting that the user is logged into the Windows VM using their Azure credetials (although that would be great)... Just that within a VM, signing into Storage Explorer using Azure credentials.

I've got as far as signing in the browser but then Storage Explorer returns an a sign in error:

image

I presume the firewall is blocking outbound connections however not sure of the implications of opening the firewall for this endpoint, and was wondering whether you'd considered this in the past?

@tim-p-allen
Copy link
Collaborator

Yes you're right, currently the firewall is blocking the signin url. We could have this as configuration option? Some users may not want to open the firewall up.

@jonnyry
Copy link
Collaborator Author

jonnyry commented May 9, 2024

So the blocked FQDN I can see in the firewall is for management.azure.com, which is also listed here:

https://learn.microsoft.com/en-us/azure/storage/common/storage-explorer-network

I'm just wondering what implications (security or otherwise) there would be of opening this to TRE users?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants