docs(e2e): document the TOTP secret invariant + mismatch recovery (BUNYIP-454) #448
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/BUNYIP-454-e2e-totp-invariant"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
BUNYIP-454 (relates BUNYIP-445). Closes the E2E 2FA saga with a docs playbook so it does not recur as folklore.
What
docs/e2e.md's 2FA provisioning section gains:--enable-2fa) andE2E_STAGING_TOTP_SECRET(Forgejo Actions secret ->E2E_TOTP_SECRET) must be byte-identical. A mismatch rejects every code and fails the FIRST 2FA submit (setup + login.spec throw "TOTP rejected on both attempts"). Forgejo secrets are write-only, so pick one base32S, set the Forgejo secret =S, and re-runBUNYIP_E2E_TOTP_SECRET=S just e2e-bootstrap --enable-2fa. Distinguished from the single-use second-login collision thatlib/login.tsretries (BUNYIP-453).Docs only.
🤖 Generated with Claude Code