Azure / Azure/BatchExplorer

Putting back adding account with SharedKey/Account Key

Open
#2,571 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
TypeScript
Stars
205
Forks
75
PR merge metrics
No merged PRs in 30d

Description

**Is your feature request related to a problem? Please describe.**

Currently starting Batch Explorer requires AAD authentication. If user rejects the AAD prompt, Batch explorer exits.
So far I don't see any settings/login prompt/add account to use URL/Account Key instead.

Not all users have Reader role access to Batch and its adjacent resources (eg Storage Accounts for autostorage), nor users' network environment allowing AAD server authentication.
A slim, direct access to Batch endpoint only feature would solve this.

It looks like there was a WIP https://github.com/Azure/BatchExplorer/pull/1586 4 years ago but probably got lost after some rebuilding from scratch.

**Describe the solution you'd like**

Can we have "Add Batch Account with Account Key" authentication mode?
Storage Explorer allows either AAD, SAS, and access key access, Batch Explorer should be able too.
![image](https://user-images.githubusercontent.com/5071602/188352691-3730c3da-1860-4efc-8f85-64d3d2a0adac.png)

I understand Account Key only allows access to Batch resource itself, so naturally storage account related operations would be blocked/fail but this would be a great feature to re-add.

Thanks

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.