Cloudbridge 2FA
This plugin provides uncomplicated 2FA functionality for WordPress. It will allow you to require a second, one time password or OTP, code to be entered when certain (or all) users attempt to log in to WordPress. The plugin supports two factor methods: six-digit codes sent by e-mail standards-based a
This plugin provides uncomplicated 2FA functionality for WordPress. It will allow you to require a second, one time password or OTP, code to be entered when certain (or all) users attempt to log in to WordPress.
The plugin supports two factor methods:
- six-digit codes sent by e-mail
- standards-based authenticator apps using TOTP
The e-mail code has a limited lifetime (defaults to 15 minutes). Once a code has been consumed, it is considered invalid.
Authenticator app setup is handled from the user’s own profile page. The plugin provides a QR code, a manual setup key, and recovery codes for when the authenticator app is not available.
You may configure that only certain roles are required to use 2FA, and it is recommended that you enable 2FA for those users with privileged access.
You may also configure the plugin to allow certain roles to enable an OTP code bypass, which sets an account-specific cookie in that user’s web browser. Several users can share a browser while keeping separate trust settings. Trusted-browser tokens expire on the server and are invalidated when the account password changes.
You can add custom text to the OTP code entry form, and you can add custom text to the OTP code e-mail message. OTP e-mails include HTML and plain-text versions with the same code, verification reference, expiry information, and custom text.
The plugin can be configured to allow it to be handled/managed only by specific users, thus making it harder for someone to accidentally or intentionally deactivate it. The implemented solution for this is by no means waterproof. If someone, for example, has access to your WordPress installation by means of FTP or similar, the plugin files can be physically removed (or moved out of your WordPress installation), which basically deactivates the plugin as well.
After upgrading to 2.0.2, users must complete 2FA once to trust a browser again. Existing pending login attempts must be restarted. Protected interactive logins must use the WordPress login page. Custom forms and XML-RPC password logins cannot complete CB2FA challenges. REST application-password authentication continues to be handled separately by WordPress. E-mail codes use the verification reference shown on the login screen. New messages are limited to one per account per minute until 2FA succeeds. Successful verification clears the mail cooldown. Existing codes keep their original expiry time when switching factors.