Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Spurious "reauthentication required" prompt immediately after signing in

已关闭
#9,111 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
50/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
冷清
技术栈
azure

调研方向

在 Linux 上使用基于 broker 的登录,通过具有已筛选的来宾租户或临时租户的帐户,在 Storage Explorer 1.44.0 中重现该问题。跟踪租户重新身份验证流程以及“需要重新身份验证”的 toast,然后验证重新身份验证成功后会加载租户订阅,且不会显示该 toast。

由索引模型根据 Issue 内容生成。

描述

:beetle: regression :computer: linux :computer: mac :gear: identity service :gear: sign-in :grey_question: need logs

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

  1. Sign into an account whose home tenant has subscriptions. The home tenant and its subscriptions load as expected.
  2. An additional tenant (e.g. a guest/ephemeral tenant) also appears in the account's tenant list but is filtered out (unchecked).
  3. Un-filter (check) that additional tenant. Storage Explorer reports that reauthentication is required for it.
  4. Reauthenticate into that tenant (the sign-in flow for the additional tenant differs slightly, as expected). Reauthentication succeeds and the tenant's subscriptions load.
  5. 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.

主要语言
没有语言数据
星标
456
派生
92
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/AzureStorageExplorer 的其他 Issue

查看 microsoft/AzureStorageExplorer 的全部 Issue

相似的 Issue

更多 Security Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。