microsoft / microsoft/AzureStorageExplorer
Support OTP login flow for guest users without AAD/MSA account (i.e. add ability to log-in to specific tenant)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Currently, when adding an Azure account to the Storage Explorer, there is no "simple" way of authenticating as a guest user using a non AAD/MSA account using the OTP authentication method (albeit, currently in preview). This functionality would be useful for scenarios when you're sharing data with external users who are authenticating via this method.
With the default authentication method in ASE, you get this error as soon as you enter a non-AAD/MSA account:

Alternatively, enabling the (preview) MSAL authentication setting in the ASE settings, which opens a browser when authenticating initially leads to the same issue:

However, since at this point we have access to the auth url, I could replace the organizations part of the path with the tenantId for the target tenant. After doing this, I could enter my non AAD/MSA account email address and start the OTP process, and sign-in successfully:

Describe the solution you'd like
Ideally, when adding an Azure account, there'd be a way to specify the tenant you want to log-in to before starting the log-in process. This would construct the correct (specific) auth endpoint (which I've done manually above) and, in doing so, would support the OTP auth flow.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Storage Explorer account-add authentication flow, including the preview MSAL authentication setting and where the auth URL is constructed. Confirm how a tenant can be selected before sign-in, then verify that the resulting tenant-specific flow supports OTP authentication for guest users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- authentication, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100