v0.2.0
This commit is contained in:
commit
f936aeb807
1 changed files with 15710 additions and 0 deletions
45
readme.txt
Normal file
45
readme.txt
Normal file
|
|
@ -0,0 +1,45 @@
|
|||
=== 2FA (by ROBOTSTXT) ===
|
||||
Contributors: robotstxt
|
||||
Tags: security, two-factor authentication, login, otp
|
||||
Requires at least: 6.4
|
||||
Tested up to: 6.4
|
||||
Requires PHP: 8.2
|
||||
Stable tag: 0.2.0
|
||||
License: GPLv3 or later
|
||||
License URI: https://www.gnu.org/licenses/gpl-3.0.html
|
||||
|
||||
Security plugin that adds a two-factor authentication flow to the WordPress login screen.
|
||||
|
||||
== Description ==
|
||||
|
||||
This plugin lets administrators enforce two-factor authentication per role and already delivers email verification codes during the login flow. After the username and password are validated, the login screen redirects to a dedicated verification step flagged with its own query parameter. The screen hides the username and password controls, automatically prioritizes authenticator apps when they are enabled, offers links to switch between authenticator, email, or recovery-code challenges, lets email users trigger an additional delivery when they need a fresh code, and auto-submits once the active method reaches its expected length (six digits for OTP, seven for email, eight for recovery codes). Users can manage their preferences from their profile, where every method starts unchecked until it is explicitly confirmed. The authenticator section now keeps the QR code and setup key visible until a valid six-digit code is entered, regenerates the secret whenever the option is disabled, and surfaces a dedicated button to issue a replacement secret. Recovery codes are shown in a two-column grid, expose the remaining count out of ten, require entering one code before activation, and automatically reset when the stored batch is exhausted so a fresh list is always available without extra clicks.
|
||||
|
||||
Administrators can remember successful verifications for a configurable duration—per login, daily, weekly, or every 28 days—and even lock the schedule so profiles inherit the global requirement. Device and IP fingerprints are stored securely to decide when a fresh challenge is needed, ensuring suspicious logins must re-validate regardless of the remembered interval.
|
||||
|
||||
== Installation ==
|
||||
|
||||
1. Upload the `robotstxt-2fa` directory to `/wp-content/plugins/`.
|
||||
2. Activate the plugin through the "Plugins" menu in WordPress.
|
||||
3. Configure the authentication options in your profile and in the Two-Factor Authentication admin menu.
|
||||
|
||||
== Frequently Asked Questions ==
|
||||
|
||||
= Is this plugin production ready? =
|
||||
|
||||
Yes. Email codes, recovery confirmations, and authenticator apps with on-site QR codes are all available, though you should still test changes in a staging environment before enforcing them across your site.
|
||||
|
||||
= How do I enable the authenticator QR code? =
|
||||
|
||||
Install the optional QR library inside this plugin directory with `composer require bacon/bacon-qr-code:^3.0`. The plugin will automatically load the Composer autoloader when it exists, enabling the QR code renderer for the OTP method.
|
||||
|
||||
== Changelog ==
|
||||
|
||||
Review the `changelog.txt` file for additional details.
|
||||
|
||||
== Upgrade Notice ==
|
||||
|
||||
= 0.2.0 =
|
||||
Authenticator apps now include on-page QR codes and recovery codes stay visible until you confirm one of them. This update also fixes the confirmation workflow and improves the QR fallback guidance when PHP extensions are missing.
|
||||
|
||||
= 0.1.0 =
|
||||
Initial version containing the basic plugin structure.
|
||||
Loading…
Reference in a new issue