[docs-scanner] 2FA account recovery instructions contain logical contradiction
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 72/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- docker
调研方向
打开 content/manuals/security/authentication/2fa/recover-hub-account.md，检查当前的 "Recover your account without access" 部分。验证 Docker 实际的登录和 2FA 恢复流程，包括丢失设备选项是在身份验证之前还是之后出现，以及是否必须填写 Contact Support 表单。完成的标准是：说明与用户体验相符，且不会给出相互矛盾的步骤。
由索引模型根据 Issue 内容生成。
描述
File: content/manuals/security/authentication/2fa/recover-hub-account.md
Issue
The "Recover your account without access" section instructs users to sign in with username and password when they've lost both their 2FA device and recovery code:
If you lost access to both your two-factor authentication application and your recovery code:
- Sign in to your Docker account with your username and password.
- Select I've lost my authentication device and I've lost my recovery code.
Why this matters
This is a logical contradiction that will confuse users in a critical account recovery situation. When 2FA is enabled on an account, signing in requires:
- Username and password
- The 2FA code from the authenticator app
If a user has lost their authentication device, they cannot provide the 2FA code, which means they cannot complete step 1 (signing in). The instructions don't explain how to bypass the 2FA prompt or access the "I've lost my authentication device" option without being able to sign in first.
A user following these instructions will be stuck at the sign-in page, unable to proceed to step 2 where they can indicate they've lost their device.
Suggested fix
Clarify the actual recovery flow. Possible approaches:
-
If there's a "lost device" link on the sign-in page itself (before completing authentication), explain that:
- Go to the sign-in page
- Enter username and password
- When prompted for 2FA code, select "I've lost my authentication device"
- Then select "I've lost my recovery code"
-
If users must contact support without being able to sign in at all, simplify to:
- If you've lost both your authentication device and recovery code, you cannot sign in
- Complete the Contact Support form with your primary email address for recovery instructions
The instructions should match the actual user experience when 2FA blocks sign-in.
Found by nightly documentation quality scanner
- 主要语言
- Markdown
- 星标
- 4.7k
- 派生
- 8.5k
- 平均合并
- 2 天 21 小时
- 30 天内合并 PR
- 129
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
docker/docs 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
status/triage
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
[docs-scanner] Container proxy table misleadingly presents nested properties as separate parameters可能已有人在做 @dave123981 于 7 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
[docs-scanner] Conflicting WSL version requirements between ECI pages可能已有人在做 @dave123981 于 8 天前认领。 未关闭
难度 1/5 1-3 小时 新手友好度 90/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
相似的 Issue
-
code quality security
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
needs triage
难度 2/5 1-3 小时 新手友好度 65/100
darnitdevorg/darnit#585 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
Agent-Threat-Rule/agent-threat-rules#654 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
XRPLF/xrpl-dev-portal#4000 ·
维护者通常 1 天内回复
-
security
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复