Spurious "reauthentication required" prompt immediately after signing in
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- azure
- Domain
- authentication, cloud
Research direction
Reproduce the issue in Storage Explorer 1.44.0 on Linux with broker-based sign-in, using an account with a filtered guest or ephemeral tenant. Trace the tenant reauthentication flow and the reauthentication-required toast, then verify that a successful reauthentication loads the tenant subscriptions without showing the toast.
Written by the indexing model from the issue text.
Description
Problem
After signing in and then successfully reauthenticating into an additional (guest/ephemeral) tenant, Storage Explorer shows a toast notification saying reauthentication is required -- even though the reauthentication just succeeded and the tenant's contents load normally. The prompt is a false alarm.
Steps to reproduce
- Sign into an account whose home tenant has subscriptions. The home tenant and its subscriptions load as expected.
- An additional tenant (e.g. a guest/ephemeral tenant) also appears in the account's tenant list but is filtered out (unchecked).
- Un-filter (check) that additional tenant. Storage Explorer reports that reauthentication is required for it.
- Reauthenticate into that tenant (the sign-in flow for the additional tenant differs slightly, as expected). Reauthentication succeeds and the tenant's subscriptions load.
- A toast notification then appears stating that reauthentication is required -- despite the reauthentication in step 4 having just succeeded.
Expected: No reauthentication toast after a tenant has just been successfully reauthenticated.
Actual: A "reauthentication required" toast appears immediately after the successful reauthentication.
Environment: Storage Explorer 1.44.0 (Linux); broker-based sign-in enabled.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 2h 7m
- Merged PRs (30d)
- 1
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from microsoft/AzureStorageExplorer
-
:beetle: regression :copilot: copilot :test_tube: testing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/AzureStorageExplorer#9191 · 1 comment ·
-
Difficulty 2/5 1-2 days Newbie friendliness 76/100
microsoft/AzureStorageExplorer#9186 ·
-
:globe_with_meridians: hard-coded string :globe_with_meridians: localization :test_tube: testing
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/AzureStorageExplorer#9152 ·
-
Sign-in errorOpen
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/AzureStorageExplorer#9206 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/AzureStorageExplorer#9204 ·
All issues in microsoft/AzureStorageExplorer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
NousResearch/hermes-agent#131271 · 1 comment ·
Maintainers usually reply within 1 day
-
failed-test failure:ai-fixable failure:insufficient-data failure:test-needs-update scout-playwright Team:Entity Analytics
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
elastic/kibana#294939 · 2 comments ·
Maintainers usually reply within 1 day
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
area: backend enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
snapotter-hq/SnapOtter#1879 ·
Maintainers usually reply within 1 day
-
area/dependencies backport/26.4 kind/cve severity/high source/scan-dependencies status/triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days