This commit is contained in:
Javier Casares 2026-06-05 14:04:51 +00:00
commit f936aeb807

42
changelog.txt Normal file
View file

@ -0,0 +1,42 @@
# Changelog
## [Unreleased]
### Added
- Authenticator app support with stored secrets and QR provisioning powered by the optional `bacon/bacon-qr-code` library.
- Recovery code confirmation workflow that requires entering one of the freshly generated codes before hiding them.
- Single-use recovery codes with profile management, one-time display, and login validation.
- Dedicated verification stage token that secures 2FA screens and allows protected email code resends.
- Admin settings page with role-based enforcement controls for two-factor authentication.
- Uninstall routine that removes stored plugin options.
- Network-wide enforcement options for WordPress multisite installations.
- Email-based verification codes with throttled delivery and expiry handling.
- Configurable verification frequency that remembers trusted devices while allowing administrators to lock the schedule per site.
### Changed
- Profile method toggles now start unchecked and require validating authenticator and recovery codes before activation, with new inline prompts and regenerated secrets when options are disabled.
- The profile screen now keeps recovery codes visible in a two-column grid until one is confirmed, shows remaining counts, and automatically refreshes the list when the stored batch is exhausted.
- Email verification now displays the destination address alongside the method label.
- The login verification screen now hides the username/password fields, exposes a back-to-login link, and supports email code resends from a dedicated query-flagged URL.
- The verification stage now enforces authenticator app codes when they are enabled and exposes secure links to switch between OTP, email, and recovery-code challenges without restarting the login.
- Promoted the settings interface to a dedicated top-level Two-Factor Authentication menu for easier discovery.
- Adjusted the Two-Factor Authentication menu position so it appears within the plugins section of the admin navigation.
- User profile settings now persist preferences and automatically enforce role-based 2FA requirements.
- The login screen now auto-submits verification forms once the active method reaches its required length (six digits for OTP, seven for email, eight for recovery codes) and removes the Remember Me control during OTP checks.
- Recovery code requests now submit through the native profile form, regenerate codes server-side, and remember the section anchor on the redirect so the refreshed screen focuses the two-factor settings.
- The refreshed profile screen renders the newly issued ten codes inside a notice, including copy controls and updated status messaging, without relying on JavaScript-driven form submissions.
- The generator button now submits the profile form directly, honours core capability checks, and shares nonce validation with the existing profile workflow.
### Fixed
- Prevented a fatal error on the profile screen by exposing the recovery code batch size helper used during rendering.
- Corrected the recovery-code confirmation flow so previews persist until acknowledged and the confirmation code is accepted.
- Hardened authenticator QR generation by catching library errors and pointing administrators to the required bacon/bacon-qr-code ^3.0 dependency.
- Improved recovery-code AJAX error handling so failed requests surface localized messages instead of silently failing.
- Forced roles now see two-factor authentication enabled with the default email method selected in their profile, and per-user data is purged during uninstall.
- Restored the login verification handlers so the authenticate filter no longer triggers fatal errors and email challenges complete successfully.
- Ensured the profile recovery-code generator always reaches `admin-ajax.php`, even when localized data is missing, so the button reliably displays the codes inline.
## [0.1.0] - 2024-04-08
### Added
- Initial skeleton for the 2FA (by ROBOTSTXT) plugin.
- Initial documentation files (`readme.txt`, `AGENTS.md`, `changelog.txt`).
- Placeholder classes for login handling, user profile integration, and admin settings.