v1.6.0
This commit is contained in:
parent
38520b2ba7
commit
fd2880bece
1 changed files with 1075 additions and 87 deletions
33
readme.txt
33
readme.txt
|
|
@ -4,7 +4,7 @@ Tags: security, two-factor authentication, login, otp
|
|||
Requires at least: 6.4
|
||||
Tested up to: 7.0
|
||||
Requires PHP: 8.0
|
||||
Stable tag: 1.5.2
|
||||
Stable tag: 1.6.0
|
||||
License: GPLv3 or later
|
||||
License URI: https://www.gnu.org/licenses/gpl-3.0.html
|
||||
|
||||
|
|
@ -59,6 +59,37 @@ Yes. Activate the plugin at the network level. Network administrators can set an
|
|||
|
||||
== Changelog ==
|
||||
|
||||
= 1.6.0 =
|
||||
|
||||
_Release date: 2026-08-07_
|
||||
|
||||
**Added**
|
||||
|
||||
* REST API for administrators (namespace `robotstxt-2fa/v1`, all endpoints require `manage_options`):
|
||||
* `GET /wp-json/robotstxt-2fa/v1/settings` — read the full 2FA configuration.
|
||||
* `PUT /wp-json/robotstxt-2fa/v1/settings` — update the configuration (reuses the same validation as the admin settings form).
|
||||
* `GET /wp-json/robotstxt-2fa/v1/users?role=<slug>&status=<enabled|required|disabled>` — list every user with their 2FA status: enabled, configured methods, role-required methods, forced flag, frequency, preferred method, whether OTP is set up, and unused recovery code count. No secrets are exposed.
|
||||
|
||||
**Changed**
|
||||
|
||||
* `wp 2fa list` now shows separate **Enabled**, **Methods** (configured), and **Required** (role-enforced) columns, plus a new `--required` filter to list only users whose role enforces 2FA.
|
||||
|
||||
= 1.5.3 =
|
||||
|
||||
_Release date: 2026-08-07_
|
||||
|
||||
**Added**
|
||||
|
||||
* Per-user preferred sign-in method — a new "Preferred method" dropdown on the user profile (visible when two or more methods are enabled) lets each user choose which verification method is requested first at the login screen. Users can still switch methods on the login screen via the existing alternate-method links.
|
||||
|
||||
**Changed**
|
||||
|
||||
* Role enforcement is now a floor, not a ceiling. When a role requires specific methods, those methods are still forced on the user's profile (enforced setup), but at login users may authenticate with any method they have configured — not only the role-required ones. Previously, users who configured extra methods (e.g. an authenticator app) only saw the role-required method at login.
|
||||
|
||||
**Fixed**
|
||||
|
||||
* Security: the "Require 2FA to create Application Passwords" check could be bypassed via the `/wp/v2/users/me/application-passwords` REST route. The route matcher now accepts the `me` alias.
|
||||
|
||||
= 1.5.2 =
|
||||
|
||||
_Release date: 2026-06-06_
|
||||
|
|
|
|||
Loading…
Reference in a new issue