Description
Add Two-Factor Authentication, Passwordless Authentication and Account Validation to your WordPress website.
Overview
This plugin adds the following major features to WordPress:
- 3 One-Time Password modes: Two-Factor Authentication, Passwordless Authentication and Account Validation.
- 3 Authentication Gateways for OTP Verification Codes: WordPress Email, Twilio SMS, Alibaba Cloud SMS ; all with option to use a sandbox mode.
- Two-Factor Authentication: allow (or force) users to authenticate with a second factor on top of their password.
- Passwordless Authentication: allow users to login simply with their username, an identifier, and an OTP Verification Code (identifier depending on the Authentication Gateway – email or phone number supported with the default gateways).
- Account Validation: force users to validate their account by entering an OTP Verification Code at first login, on a set regular basis at login, or at each login.
- Synchronize OTP identifiers with existing data: wish to use Twilio SMS, but already have a phone number field saved in database? Perhaps with the “Billing Phone” in WooCommerce? Use this field by indicating its user meta key in the gateway settings (Note: duplicate identifiers will require users to choose a different one on update).
- Simple yet customizable appearance: forms used to request OTP Verification Codes use a neutral dedicated style compatible with most themes, with customizable logo and call-to-action colors.
- Activity Logs: when enabled, administrators can follow the activity of the enabled gateway. Critical messages regarding gateway malfunction are always logged.
- Customizable for developers: developers can add their own gateways or add custom One-Time Password modes using action and filter hooks, and more – see the developers documentation.
- Integration-friendly: specific integration with Ultimate Member and WooCommerce is included by default ; developers can easily plug into OTP Authenticator with a multitude of functions, filter hooks and action hooks – see the developers documentation – contributions to integrations are welcome.
- Unlimited features: there are no premium version feature restrictions shenanigans – OTP Authenticator is fully-featured right out of the box.
Troubleshooting
OTP Authenticator is regularly updated, and bug reports are welcome, preferably on Github, especially for advanced troubleshooting.
Each bug report will be addressed in a timely manner, but general inquiries and issues reported on the WordPress forum may take significantly longer to receive a response.
Only issues occurring with included integrated plugins (or plugin features), core WordPress and default WordPress themes (incl. WooCommerce Storefront) will be considered without compensation.
Troubleshooting involving 3rd-party plugins or themes will require compensation in any case, and will not be addressed on the WordPress support forum.
Integrations
Although OTP Authenticator is designed to work out of the box with most combinations of WordPress plugins and themes, there are some edge cases necessitating integration, with code included in the core files of OTP Authenticator executing under certain conditions.
Integrations added to core are limited to popular plugins and themes: any extra code specific to a handful of installations require a separate custom integration plugin not shared with the community (decision at the discretion of the OTP Authenticator plugin author).
If such need for plugin integration arises, website administrators may contact the author of OTP Authenticator to become a patron.
All integrations are to be funded by plugin users, with downpayment and delivery payment, at the plugin author’s discretion, without exception.
The patron in return may be credited with their name (or company name) and a link to a page of their choice in the plugin’s Changelog.
Installation
This section describes how to install the plugin and get it working.
- Upload the plugin files to the
/wp-content/plugins/otpadirectory, or install the plugin through the WordPress plugins screen directly for all websites to connect together - Activate the plugin through the ‘Plugins’ screen in WordPress
- Edit plugin settings – follow on-screen help if necessary
FAQ
Where to find more help?
More help can be found on the WordPress support forum for general inquiries and on Github for advanced troubleshooting, integration, and feature requests.
Help is provided without compensation for general enquiries and bug fixes only: feature requests, extra integration or conflict resolution with third-party themes or plugins, and specific setup troubleshooting requests will not be addressed without a fee (transfer method and amount at the discretion of the plugin author).
Screenshots











Changelog
2.0
- Require PHP 8.3 and declare compatibility with WordPress 7.1
- Update the Twilio and Alibaba Cloud SMS libraries through Composer and remove library security warnings
- Add a deployment script for creating release packages
- Add PHP and browser tests for settings, gateways, passwordless login, two-factor authentication, account validation, and security rules
- Restrict Passwordless Authentication to selected WordPress roles and show a clear error when a user’s role is not included
- Select Subscriber as the default Passwordless Authentication role, restore it when no role remains selected, and allow another role to replace it
- Display Two-Factor Authentication switch labels above the button by default and add an option to display them inline
- Require server-side permissions for administrative account-validation and two-factor controls
- Bind each verification code to one purpose and store simultaneous two-factor, account-validation, and passwordless codes separately
- Keep a valid verification code available after an incorrect attempt until it expires or reaches the configured attempt limit
- Prevent passwordless requests from revealing codes, changing the selected account, depending on client IP addresses, or being reused by another browser
- Restrict every post-authentication redirect to a safe address on the current WordPress site
- Require administrator permission and a valid request token before activity logs can be read or erased
- Prevent the Ultimate Member integration from creating PHP objects from submitted form data
- Keep Two-Factor Authentication switch text as plain text when its state changes
- Restore the previous WordPress user after every passwordless request and verification, including unexpected failures
- Restrict delivery-address enrollment so an existing address cannot be replaced while authentication is pending
- Block protected REST, administration, background, front-end, WooCommerce, and XML-RPC requests until required authentication or validation is complete
- Reject the first password-only XML-RPC request for accounts requiring two-factor authentication or account validation
- Record request waiting periods only after successful delivery and protect simultaneous requests with an expiring, owner-checked server lock
- Correct toolbar visibility, supplied-user checks, request retry behavior, and failed-delivery handling
- Correct WordPress email defaults, saved subject handling, and identifier synchronization on the first email change
- Correct direct account validation through the public helper function
- Add a minimal working custom Authentication Gateway example to the developer documentation
- Refresh the translation template with all new interface and error messages
- Make every PHP code style exception comment name the exact rule it skips
- Improve PHP 8.4 compatibility, WordPress coding-style compliance, input handling, output escaping, documentation, and static-analysis results
1.1
- Update Alibaba library
- Add functin
otpa_is_email_gateway - Fix bugs when using email gateway
1.0
- First version
