Linux 软件免费装

MksDdn Reddy Auth

开发者 mksddn
更新时间 2026年6月11日 16:17
PHP版本: 7.4 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

login otp authentication rest-api

下载

1.0.0 1.1.0

详情介绍:

MksDdn Reddy Auth provides OTP-based authentication with: The plugin maps each Reddy ID to a WordPress user and can create an account automatically on first successful login.

安装:

  1. Upload the plugin to the /wp-content/plugins/ directory.
  2. Activate the plugin through the Plugins menu in WordPress.
  3. Open Settings > Reddy Auth and configure bot token and security options.
  4. Create a login page and add the shortcode [mksddn_reddy_login].
  5. If site protection is enabled, select that page in the Login page setting (otherwise guests are redirected to wp-login.php fallback).

常见问题:

Where should I store the bot token?

Use the MKSDDN_REDDY_BOT_TOKEN constant in wp-config.php on production sites. The settings page field is a development fallback and should not replace secure server-side configuration in live environments.

Why am I stuck in a redirect loop?

This usually happens when Protect site content is enabled but no valid login page is selected. Create a page with [mksddn_reddy_login], choose it in Login page, and save settings.

Does this plugin replace /wp-login.php?

No. It adds a Reddy OTP login flow via shortcode and REST endpoints. Standard WordPress login may still be available unless you restrict it separately.

Are WordPress users created automatically?

Yes. On first successful OTP login the plugin creates a WordPress user mapped to the Reddy ID and stores the mapping in user meta.

How do REST clients authenticate?

Send issue_token: true in the login request, then pass the returned token in the Authorization: Bearer header. REST login does not set a WordPress cookie unless you also send issue_session: true. Use the login shortcode or issue_session: true when the browser needs access to Protect site content pages.

What is the difference between issue_token and issue_session?

issue_token returns a Bearer token for REST API clients. issue_session sets the WordPress auth cookie. Shortcode login always sets a cookie. REST login sets a cookie only when issue_session is true (default false). Headless integrations should use issue_token without issue_session so site content stays locked until an explicit cookie login.

What happens when an administrator deletes a Reddy user?

All plugin Bearer tokens for that WordPress user are revoked and WordPress session tokens are destroyed. The user must complete OTP login again. Deleting the WordPress account does not permanently block the Reddy ID; a successful OTP login can recreate the account.

Why do I get HTTP 429?

The plugin rate-limits OTP send and login attempts per Reddy ID and client IP. Wait for the limit window to expire or adjust limits in Settings > Reddy Auth.

What does Allowed request sources do?

It optionally checks Origin or Referer on plugin REST routes only. Empty list = no restriction (default). Non-empty list = browser apps must call from a listed URL. It does not replace OTP, rate limits, or Bearer auth—headers can be spoofed.

Why do I get HTTP 403 with "Request not allowed from this source"?

Allowed request sources is configured and the request has no matching Origin/Referer. Add your frontend URL to the list, send a matching Origin header from server clients, leave the list empty for backends, or use the mksddn_reddy_is_request_url_allowed filter.

Which data does the plugin store?

Settings in WordPress options, Reddy ID mapping in user meta, Bearer token hashes in a custom database table, and OTP/rate-limit state in transients. Raw OTP codes and raw tokens are not stored.

What happens on uninstall?

If uninstall cleanup runs, plugin-owned options, user meta, custom tables, and transients are removed according to uninstall.php.

更新日志:

1.1.0 1.0.0 0.1.4 0.1.3 0.1.2 0.1.1 0.1.0