There should be an option to generate a new set of scratch codes. Either for when you reach your last two valid ones, or in case you actually have lost your set of scratchcodes.
Rather than having to fully disable 2FA and re-enable it.
| TheDJ | |
| Nov 13 2016, 9:46 AM |
| F65750465: image.png | |
| Aug 14 2025, 9:29 AM |
| F65746189: image.png | |
| Aug 13 2025, 5:19 AM |
There should be an option to generate a new set of scratch codes. Either for when you reach your last two valid ones, or in case you actually have lost your set of scratchcodes.
Rather than having to fully disable 2FA and re-enable it.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T125653 Create new types of notifications | |||
| Open | None | T100375 Improve user experience of Two-Factor process | |||
| Open | None | T352856 Recovery code improvements | |||
| Resolved | None | T166622 Allow all users on all wikis to use OATHAuth | |||
| Resolved | Reedy | T131788 Users should be notified when only two recovery codes are left | |||
| Duplicate | None | T399651 Separate recovery codes into a separate module | |||
| Resolved | sbassett | T150601 Add option to generate new set of recovery codes | |||
| Resolved | sbassett | T232336 Separate recovery codes into a separate 2FA module | |||
| Resolved | taavi | T242031 Allow multiple different 2FA devices | |||
| Resolved | Reedy | T268564 Convert OATHAuth to AbstractSchema | |||
| Resolved | taavi | T330502 Create oathauth_types and oathauth_devices tables | |||
| Resolved | Marostegui | T348693 Drop oathauth_users table from production | |||
| Resolved | sbassett | T145915 OATHAuth OTP shouldn't be stored in cleartext in the DB |
UI design by @AAlhazwani-WMF (for more context on the proposed UI refresh for 2FA, see T401771 and T401774):
@Catrope i've realized the the full flow was missing in figma, so i've created a new section under the 'user stories' page, here's the direct link https://www.figma.com/design/ll2DMOlp80iy7wYCk44dxT/Multiple-Authenticators?node-id=4305-7374&t=NrkuFI0ZQaicGjZy-1 to the section in question.
Marking as resolved with the completion of T232336. There are some small UI tweak that are tracked in separate bugs for the continuing FY2025-26 WE 4.6 - Account Security (WE 4.6.4 - 2FA improvements and passkey support).