Linux 软件免费装
Banner图

Super Duper Two-Factor Login

开发者 rogerruckstuhl
更新时间 2026年5月13日 16:16
PHP版本: 8.0 及以上
WordPress版本: 6.9
版权: GPL-2.0-or-later
版权网址: 版权信息

标签

security login totp 2fa two-factor

下载

2.5.12 2.5.13 2.5.5 2.5.9 2.5.11

详情介绍:

Super Duper Two-Factor Login adds robust two-factor authentication to your WordPress site. Unlike many alternatives, this plugin is completely free – no hidden costs, no premium tiers, no upsells. Every feature is included from the start. 🇨🇭🇩🇪🇦🇹 Hinweis für DACH-Nutzer: Plugin und Support sind auf Deutsch (Schweiz/Deutschland/Österreich) verfügbar. Alle Texte und Einstellungen sind vollständig auf Deutsch übersetzt. Fully translated out of the box in German (Switzerland, Germany, Austria), English, French, Spanish, Italian and Dutch – no separate language pack required. Two Verification Methods Comprehensive Fallback System Enforcement & Trust Integration Security Privacy & Hardening (optional) {"id":1,"name":"Author","url":"","description":"","link":"https:\/\/example.com\/","slug":"author","avatar_urls":{}}

安装:

  1. Upload the plugin via Plugins → Add New → Upload Plugin, or install it directly from the WordPress plugin directory.
  2. Activate the plugin.
  3. Configure the main 2FA settings under Two-Factor Login in the admin menu. Optional Privacy & Hardening features (REST user-data masking, author-archive blocking, password-reset lock-down, users-list status column) are on the same settings page.
  4. Users can set up 2FA from their WordPress profile page or WooCommerce My Account.

屏幕截图:

  • Setup prompt asking the user to start now or later
  • Choosing the authentication method: email or authenticator app
  • App-based authentication – FreeOTP recommended, with download links
  • Email-based authentication
  • Email confirmation step
  • Backup codes – send by email, download, or print
  • Shortcode displaying the 2FA status on any page
  • 2FA status on the user's My Account page – inactive
  • 2FA status on the user's My Account page – active, with the chosen method
  • Backend admin view: per-account 2FA status and the method in use
  • Settings: enforcement reminder, which roles must use 2FA, grace period, enforcement areas, validation strictness (strict / normal / tolerant), and trusted-device duration
  • Shortcode for embedding the 2FA status indicator on any page
  • Privacy & Hardening: hide user data in the REST API and disable password reset per role

升级注意事项:

2.5.9 Larger, more readable fonts on the forced setup screen. All translations now 100% complete in all eight supported locales. 2.5.8 Critical fix continued: forced 2FA setup AJAX returned 403 because of nonce-validation issues for unauthenticated users. Now uses token-based authorization on the login screen. 2.5.7 Critical fix: forced 2FA setup on the login screen was non-functional. The "Set up now" button now properly opens the setup flow. 2.5.6 Important fixes: REST API user data is now protected by a strict whitelist (so future SEO/page-builder plugins that add user fields are automatically covered), with a sdtfa_rest_user_allowed_keys filter for legitimate exceptions. Also fixed the "Set up now" button on the admin notice. 2.5.5 Internal compatibility fix that allows the package to pass the WordPress.org SVN pre-commit linter. No functional changes. 2.5.4 Fixes three strings in the en_US translation that accidentally contained German text. English-locale sites will now show correct English wording on the settings page and notices. 2.5.3 i18n cleanup: removed remaining hardcoded German strings from PHP and JavaScript so the plugin can be fully translated through the standard gettext workflow. 2.5.2 Fix: 2FA email codes were silently dropped on hosts that require an explicit "From" header. The setup email now sends reliably and surfaces the real error if delivery still fails. 2.5.1 New "SDTFA" column on the Users list shows actual 2FA status. Removes duplicate columns added by host mu-plugins or other 2FA plugins. 2.5.0 New optional Privacy & Hardening features: hide REST user data, block author archive enumeration, disable password reset for admins/roles. Plus a small admin UI fix for the datepicker container. 2.4.1 Bugfix: the × button on the admin notice now works correctly. 2.4.0 WordPress.org compliance release: new distinctive name, admin notice instead of auto-popup, proper enqueuing of all assets, corrected menu position. 2.3.0 First public release. Install and activate to add two-factor authentication to your WordPress site.

常见问题:

Which authenticator apps are supported?

Any TOTP-compatible app works, including Google Authenticator, FreeOTP+, Authy, Microsoft Authenticator, and many others. We recommend FreeOTP+ (Android) and FreeOTP (iOS) as free, open-source options.

What happens if I lose my phone?

You can log in using one of your 10 backup codes. If those are also gone, administrators can use their personal recovery key on the login page. As a last resort, create an empty file named .sdtfa-recovery in wp-content/ via FTP to temporarily disable 2FA.

Can I enforce 2FA for all users?

Yes. Go to Two-Factor Login settings and select which roles must use 2FA. You can set a grace period with a deadline, or enforce it immediately – users will then be required to complete 2FA setup on the login page before gaining any access.

Does this plugin work with WooCommerce?

Yes. It adds a "Two-Factor Authentication" tab to the WooCommerce My Account page. You can also enforce 2FA for the WooCommerce account area and checkout.

What is the "Trust this device" feature?

When enabled by the admin, users can check "Save this computer" during login. The 2FA code won't be required again on that device for the configured number of days.

Are external services or images used?

No. Everything runs locally. QR codes are generated in PHP, TOTP calculations happen on the server, and app store badges use local SVG files. No external images, scripts, or API calls are made.

What does the "Privacy & Hardening" section do?

It bundles four optional, independently toggleable features that close common WordPress information-leak and lock-out paths. Hide user data (REST API) replaces sensitive fields (name, slug, link, avatar) with neutral values for unauthenticated requests, while keeping the endpoint reachable so SEO and import plugins still work. Block author archives redirects unauthenticated visitors away from ?author=N and /author/<slug>/ to prevent user enumeration. Disable password reset blocks the "Lost your password?" function for administrators and/or selected roles. The users-list column adds a clean "SDTFA" status indicator on Users → All Users. All four features are off by default except the users-list column, which is on by default to clean up duplicate columns from other plugins.

Why does the Users → All Users page show an "SDTFA" column instead of a generic "2FA" one?

Some hosts and other 2FA plugins inject their own "2FA" column on the users list. When Super Duper Two-Factor Login is installed, those columns can show outdated or misleading status (for example a red ✗ even though 2FA is configured here). The plugin replaces them with a single, accurate "SDTFA" column that reads the real status from this plugin's own user meta. If you prefer the original column behavior, you can disable this in the Privacy & Hardening section.

Will this plugin conflict with other 2FA plugins?

It is not designed to run side-by-side with another active 2FA plugin – two plugins both intercepting wp-login.php will produce unpredictable results. If you are migrating from another 2FA plugin, deactivate the other one first. The "SDTFA" users-list column will hide a leftover column from a deactivated plugin only if that plugin still injects it; in normal cases the foreign column simply disappears with the foreign plugin.

Is this plugin really free?

Yes, completely. There is no premium version, no upsells, and no feature restrictions. All features are available to everyone.

更新日志:

2.5.13 – 13.05.2026 2.5.12 – 11.05.2026 2.5.11 – 05.05.2026 2.5.9 – 05.05.2026 2.5.8 – 05.05.2026 2.5.7 – 05.05.2026 2.5.6 – 05.05.2026 2.5.5 – 01.05.2026 2.5.4 – 30.04.2026 2.5.3 – 30.04.2026 2.5.2 – 30.04.2026 2.5.1 – 30.04.2026 2.5.0 – 30.04.2026 2.4.1 – 22.04.2026 2.4.0 – 22.04.2026 2.3.0 – 10.04.2026 1.0.0 – 2.2.x