| 开发者 |
gotechark
yogid |
|---|---|
| 更新时间 | 2026年6月5日 14:59 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
wp-content/uploads/loginarmor-email-2fa/loginarmor-debug.logREMOTE_ADDR by default.
/wp-content/plugins/loginarmor-email-2fa/ directory, or install the plugin through the WordPress plugins screen.Yes. You can apply 2FA by user role, by specific users, or both.
They can use a recovery code if one has been generated and saved.
Yes. You can customize the sender email address, subject line, and login code email template from the plugin settings.
No. It works with your WordPress site and its email sending setup.
Recovery codes are available from the user profile area and are intended to be saved by the user for emergency access.
No. WordPress application passwords used for REST API access bypass the OTP flow by design. 2FA applies only to interactive browser-based logins via wp-login.php.
XML-RPC logins for accounts that have 2FA enabled will be blocked with a clear error message. This is intentional — XML-RPC cannot complete an OTP challenge. If you rely on XML-RPC for a specific integration, either exclude that user from 2FA targeting or switch to application passwords, which are fully supported.
By default the plugin reads REMOTE_ADDR for IP-based rate limiting, which may be the proxy's IP rather than the real visitor's. Use the la2fa_get_client_ip filter (see Developer notes in the Description tab) to supply the correct IP for your hosting environment.
la2fa_get_client_ip filter to allow sites behind reverse proxies (Cloudflare, load balancers) to supply the correct visitor IP for rate limiting.