Modifies the Google Authenticator plugin so that only users with 2FA enabled are prompted for the authentication token.
| Author: | Ian Dunn (profile at wordpress.org) |
| WordPress version required: | 4.4 |
| WordPress version tested: | 4.9.18 |
| Plugin version: | 0.7 |
| Added to WordPress repository: | 11-12-2013 |
| Last updated: | 23-04-2021
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
| Rating, %: | 92 |
| Rated by: | 10 |
| Plugin URI: | http://wordpress.org/plugins/google-authentic... |
| Total downloads: | 18 880 |
| Active installs: | 600+ |
Click to start download
|
The Google Authenticator plugin is a great way to add two-factor authentication to your site, but it does have one major drawback: it asks every user for the authentication token, regardless of whether they have 2FA enabled or not. This can be confusing for users, which prevents some administrators from using the plugin on multi-user sites.
This plugin modifies the way that Google Authenticator behaves so that only users who have it enabled are prompted for the token. If a user doesn’t have it enabled, then they’ll proceed directly to the Administration Panels; if they do have it enabled then they’ll be prompted to enter their 2FA code.
Screenshots
The token prompt no longer appears on the initial login screen
If a user has two factor auth enabled, they'll see the prompt on a secondary screen, after they login
Does this replace the Google Authenticator plugin?
No, this is built on top of the Google Authenticator plugin and requires it in order to work.
Is this plugin secure?
I’ve done my best to ensure that it is, but just in case I missed anything I also offer a security bounty for any vulnerabilities that can be found and privately disclosed in any of my plugins.
What should I do if I can’t login?
Since this plugin integrates tightly with the Google Authenticator plugin, it’s possible that at some point in the future, changes in Google Authenticator will break the customized login process that this plugin implements. If that happens, I’ll release an updated version of this plugin to make it compatible with the new changes.
You may have difficulty installing the updated version if you can’t login, though, so you’ll need to deactivate this plugin by some alternate means, and then update it before re-activating it.
There are several alternate methods of deactivating the plugin: you can delete it via S/FTP, or by changing a database option in phpMyAdmin, or you can ask your hosting company to delete the plugin for you.
ChangeLog
v0.7 ()
- [SECURITY] Hardening against low-severity vulnerability where against application passwords were susceptible to timing attacks.
- [UPDATE] Minor cleanup.
v0.6 (2016-04-28)
- [SECURITY] Harden nonce verification to mitigate by-passing regular password authentication. This is a preventative step against a theoretical attack vector, not a response to a proven vulnerability. For more details, see https://github.com/julien731/WP-Google-Authenticator/issues/11.
- [FIX] Add support for using application passwords with email addresses instead of only usernames (new in WordPress 4.5).
- [FIX] Resolve conflict with Theme My Login plugin by checking for login header/footer functions.
v0.5 (2014-06-22)
- [FIX] The ‘Remember Me’ flag is no longer ignored when logging in.
- [NEW] Added an automated acceptance test suite. Alliteration FTW!
v0.4 (2013-12-30)
- [UPDATE] Added support for new application password format in Google Authenticator 0.45
v0.3 (2013-12-20)
- [NEW] Focus automatically set on token input field
v0.2 (2013-12-11)
- [FIX] User with valid username/password no longer temporarily logged in before entering 2FA token. Prevents leaking auth cookies. props cathyjf
v0.1 (2013-12-10)
