跳至主要內容
WordPress.org

Taiwan 正體中文

  • 佈景主題目錄
  • 外掛目錄
  • 最新消息
  • 技術支援
  • 關於我們
  • 團隊
  • 取得 WordPress
取得 WordPress
WordPress.org

Plugin Directory

ShivWeb Login Verification

  • 提交外掛
  • 我的最愛
  • 登入
  • 提交外掛
  • 我的最愛
  • 登入

ShivWeb Login Verification

由 shivweb 開發
下載
  • 詳細資料
  • 使用者評論
  • 安裝方式
  • 開發資訊
技術支援

外掛說明

ShivWeb Login Verification adds two-factor authentication (2FA) to your WordPress login using email codes. A user signs in with their password as usual, then the plugin emails them a short login code and holds the session until the code is entered. Someone who has stolen a password but cannot open the user’s inbox stays locked out.

There is no authenticator app to set up, no external service to sign up for, and no API keys. Codes are sent through your site’s own email, so any SMTP plugin you already use handles delivery, and everything runs on your server.

How a login works

  1. The user enters their username and password as normal.
  2. The plugin emails them a one time code (OTP) and holds the session.
  3. They type the code on the verification screen and continue exactly where they were going.

Choose who needs a code

Enforcement is role based. Tick the roles that should verify and leave the rest alone. By default only the Customer role is gated, so a store can protect shopper accounts without changing how the team logs in. Users can also mark a browser as trusted for a number of days you choose, so regulars are not asked for a code on every visit.

Built so you cannot lock yourself out

Enforcement stays off until you prove email delivery works: the plugin asks you to send yourself a test code and enter it before the feature can be switched on. So a broken mailer can never lock everyone out. And if anything ever goes wrong later, one line in wp-config.php or one WP-CLI command turns everything off and releases every held session immediately.

Works with WooCommerce, including the block checkout

Most login verification plugins add a field to the login form. The WooCommerce block checkout never shows that field, because it signs customers in through the Store API in the background. This plugin works differently: it verifies the session after login, on the server, so wp-login.php, wp-admin, My Account, the classic checkout and the block checkout are all covered by the same check. Nothing depends on the browser, so it cannot be skipped by calling an endpoint directly.

Email verification at registration

Optionally require new sign-ups to confirm their email address with a code before their first session works. A small popup verifies the address right on the register form, checkout registrations are verified just after, and abandoned unverified accounts are cleaned up automatically after a grace period.

Features

  • Two-factor authentication with email login codes, no authenticator app needed
  • Role based enforcement: choose exactly which user roles must verify
  • WooCommerce ready: My Account, classic checkout, and the block checkout
  • Trusted devices: remember a browser for a number of days you choose
  • Email verification for new registrations, with automatic cleanup
  • Rate limiting on every layer: resend cooldown, attempt lockout, and per-account send caps
  • Customizable email template and on-screen messages
  • No external service, no API keys, no per-message fees, no tracking
  • Recovery built in: a wp-config.php constant and WP-CLI commands

Recovery

If you ever lock yourself out, add define( 'SWLV_DISABLE_OTP', true ); to wp-config.php, or run wp swlv disable with WP-CLI. Both release every held session immediately. To unstick a single user (send limit reached, mailbox typo), run wp swlv reset-user <id|login|email>.

安裝方式

  1. Install and activate the plugin. Nothing is enforced yet.
  2. Go to Settings, then Email Verification.
  3. Choose the roles that should verify, send yourself a test code, enter it, tick “Require a code at login”, and save.

常見問題集

Is this two-factor authentication?

Yes, the email variant: the password is something the user knows, and the code proves control of their mailbox. It is the same email method WordPress’s own Two-Factor plugin offers. An authenticator app is stronger in the strict sense, but an email code still stops anyone who only has the password, which is how most accounts are broken into.

Does it work with the WooCommerce block checkout?

Yes. The block checkout logs customers in over the Store API, which the plugin refuses for unverified sessions, and a small script guides the shopper to the verification screen.

Does it send email through its own service?

No. All email goes through wp_mail(). Use any SMTP plugin you like for reliable delivery.

What happens if email delivery breaks after I enable it?

Affected users cannot verify, but you can always recover with the wp-config.php constant or WP-CLI, both documented above. Administrators are not gated by default.

The code email is not arriving. What should I check?

Check the spam folder first. The screen lets you request a new code after a short cooldown. If nothing arrives at all, the site’s email delivery is the usual cause: the site owner can go to Settings, then Email Verification, and send themselves a test code. If that fails too, install an SMTP plugin and test again. A single stuck user can always be released with wp swlv reset-user.

I enabled it, but nobody is asked for a code

Three things are expected behavior here. Sessions that were already logged in before you enabled enforcement are never challenged, only new logins are. A browser remembered through “Trust this device” skips the code until the trust expires. And only the roles you ticked are gated, so check the role of the account you are testing with, and note that administrators are not gated by default.

What data does the plugin store?

Codes are never stored, not even hashed alone: only keyed hashes live inside the WordPress session record, and they disappear when the session ends. Beyond that the plugin keeps one settings option, per-user send counters and trusted-device hashes in user meta, short-lived self-expiring transients for registration challenges and rate limits, and one cookie for “Trust this device”. There are no external services and nothing leaves your site. Uninstalling removes all of it. On shared computers, leave “Trust this device” unticked.

使用者評論

這個外掛目前沒有任何使用者評論。

參與者及開發者

以下人員參與了開源軟體〈ShivWeb Login Verification〉的開發相關工作。

參與者
  • shivweb

將〈ShivWeb Login Verification〉外掛本地化為台灣繁體中文版

對開發相關資訊感興趣?

任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄。

變更記錄

1.0.0

  • Initial release.

中繼資料

  • 版本 1.0.0
  • 最後更新 1 個月前
  • 啟用安裝數 少於 10 次
  • WordPress 版本需求 7.0 或更新版本
  • 已測試相容的 WordPress 版本 7.1.2
  • PHP 版本需求 8.2 或更新版本
  • 語言
    English (US)
  • 標籤:
    email verificationlogin securityotptwo factor authenticationwoocommerce
  • 進階檢視

評分

這個項目尚無任何評論記錄。

撰寫評分

查看全部使用者評論

參與者

  • shivweb

技術支援

使用者可在技術支援論壇提出意見反應或使用問題。

檢視技術支援論壇

  • 關於我們
  • 最新消息
  • 主機代管
  • 隱私權
  • 展示網站
  • 佈景主題目錄
  • 外掛目錄
  • 區塊版面配置目錄
  • Learn
  • 技術支援
  • 開發者資源
  • WordPress.tv ↗
  • 共同參與
  • 活動
  • 贊助基金會 ↗
  • Swag ↗
  • WordPress.com ↗
  • Matt ↗
  • bbPress ↗
  • BuddyPress ↗
WordPress.org
WordPress.org

Taiwan 正體中文

  • 查看我們的 X (之前的 Twitter) 帳號
  • 造訪我們的 Bluesky 帳號
  • 造訪我們的 Mastodon 帳號
  • 造訪我們的 Threads 帳號
  • 造訪我們的 Facebook 粉絲專頁
  • Visit our Instagram account
  • Visit our LinkedIn account
  • 造訪我們的 TikTok 帳號
  • Visit our YouTube channel
  • 造訪我們的 Tumblr 帳號
程式碼,如詩
The WordPress® trademark is the intellectual property of the WordPress Foundation.