콘텐츠로 바로가기
WordPress.org

한국어

  • 테마
  • 플러그인
  • 소식
    • 문서
    • 포럼
  • About
    • WordPress 6.9
    • 워드프레스 6.8
    • 워드프레스와 40% 웹을 위한 여정
    • 워드프레스 번역 핸드북
  • 워드프레스 한국팀
  • 워드프레스 받기
워드프레스 받기
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.

FAQ

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
  • 최근 업데이트: 2주 전
  • 활성화된 설치 10보다 적음
  • 워드프레스 버전 7.0 또는 그 이상
  • 다음까지 시험됨: 7.1
  • PHP 버전 8.2 또는 그 이상
  • 언어
    English (US)
  • 태그:
    email verificationlogin securityotptwo factor authenticationwoocommerce
  • 고급 보기

평점

아직 제출된 리뷰가 없습니다.

Your review

모든 리뷰 보기

기여자

  • shivweb

지원

할 말 있으신가요? 도움이 필요하신가요?

지원 포럼 보기

  • 소개
  • 뉴스
  • 호스팅
  • 개인정보
  • 쇼케이스
  • 테마
  • 플러그인
  • 패턴
  • 배우기
  • 지원
  • 개발자 도구
  • WordPress.tv ↗
  • 참여하기
  • 이벤트
  • 기부하기 ↗
  • Swag ↗
  • WordPress.com ↗
  • Matt ↗
  • bbPress ↗
  • BuddyPress ↗
WordPress.org
WordPress.org

한국어

  • X(이전 트위터) 계정 방문하기
  • 블루스카이 계정 방문하기
  • 마스토돈 계정 방문하기
  • 스레드 계정 방문하기
  • 페이스북 페이지 방문하기
  • 인스타그램 계정 방문하기
  • LinkedIn 계정 방문하기
  • 틱톡 계정 방문하기
  • 유튜브 채널 방문하기
  • 텀블러 계정 방문하기
코드는 詩다
The WordPress® trademark is the intellectual property of the WordPress Foundation.