| 1 |
=== Google Authenticator === |
| 2 |
Contributors: Henrik.Schack |
| 3 |
Donate Link: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=henrik%40schack%2edk&lc=US&item_name=Google%20Authenticator&item_number=Google%20Authenticator&no_shipping=0&no_note=1&tax=0&bn=PP%2dDonationsBF&charset=UTF%2d8 |
| 4 |
Tags: authentication,otp,password,security,login,android,iphone,blackberry |
| 5 |
Requires at least: 3.5 |
| 6 |
Tested up to: 3.5 |
| 7 |
Stable tag: 0.44 |
| 8 |
|
| 9 |
Google Authenticator for your WordPress blog. |
| 10 |
|
| 11 |
== Description == |
| 12 |
|
| 13 |
The Google Authenticator plugin for WordPress gives you two-factor authentication using the Google Authenticator app for Android/iPhone/Blackberry. |
| 14 |
|
| 15 |
If you are security aware, you may already have the Google Authenticator app installed on your smartphone, using it for two-factor authentication on Gmail/Dropbox/Lastpass/Amazon etc. |
| 16 |
|
| 17 |
The two-factor authentication requirement can be enabled on a per-user basis. You could enable it for your administrator account, but log in as usual with less privileged accounts. |
| 18 |
|
| 19 |
If You need to maintain your blog using an Android/iPhone app, or any other software using the XMLRPC interface, you can enable the App password feature in this plugin, |
| 20 |
but please note that enabling the App password feature will make your blog less secure. |
| 21 |
|
| 22 |
== Installation == |
| 23 |
1. Make sure your webhost is capable of providing accurate time information for PHP/WordPress, ie. make sure a NTP daemon is running on the server. |
| 24 |
2. Install and activate the plugin. |
| 25 |
3. Enter a description on the Users -> Profile and Personal options page, in the Google Authenticator section. |
| 26 |
4. Scan the generated QR code with your phone, or enter the secret manually, remember to pick the time based one. |
| 27 |
You may also want to write down the secret on a piece of paper and store it in a safe place. |
| 28 |
5. Remember to hit the **Update profile** button at the bottom of the page before leaving the Personal options page. |
| 29 |
6. That's it, your WordPress blog is now a little more secure. |
| 30 |
|
| 31 |
== Frequently Asked Questions == |
| 32 |
|
| 33 |
= The iPhone app keeps telling me I'm trying to scan an authentication token barcode that isn't valid, what to do ? = |
| 34 |
|
| 35 |
Apparently the iPhone app won't accept a barcode containing space characters in the description, removing space characters in the description should fix the problem. |
| 36 |
|
| 37 |
= Can I use Google Authenticator for WordPress with the Android/iPhone apps for WordPress? = |
| 38 |
|
| 39 |
Yes, you can enable the App password feature to make that possible, but notice that the XMLRPC interface isn't protected by two-factor authentication, only a long password. |
| 40 |
|
| 41 |
= I want to update the secret, should I just scan the new QR code after creating a new secret? = |
| 42 |
|
| 43 |
No, you'll have to delete the existing account from the Google Authenticator app on your smartphone before you scan the new QR code, that is unless you change the description as well. |
| 44 |
|
| 45 |
= I am unable to log in using this plugin, what's wrong ? = |
| 46 |
|
| 47 |
The Google Authenticator verification codes are time based, so it's crucial that the clock in your phone is accurate and in sync with the clock on the server where your WordPress installation is hosted. |
| 48 |
|
| 49 |
If you have an Android phone, you can use an app like [ClockSync](https://market.android.com/details?id=ru.org.amip.ClockSync) to set your clock in case your Cell provider doesn't provide accurate time information |
| 50 |
|
| 51 |
Another option is to enable "relaxed mode" in the settings for the plugin, this will enable more valid codes by allowing up to a 4 min. timedrift in each direction. |
| 52 |
|
| 53 |
= I have several users on my WordPress installation, is that a supported configuration ? = |
| 54 |
|
| 55 |
Yes, each user has his own Google Authenticator settings. |
| 56 |
|
| 57 |
= During installation I forgot the thing about making sure my webhost is capable of providing accurate time information, I'm now unable to login, please help. = |
| 58 |
|
| 59 |
If you have SSH or FTP access to your webhosting account, you can manually delete the plugin from your WordPress installation, |
| 60 |
just delete the wp-content/plugins/google-authenticator directory, and you'll be able to login using username/password again. |
| 61 |
|
| 62 |
= I don't own a Smartphone, isn't there another way to generate these secret codes ? = |
| 63 |
Yes, there is a Chrome browser extension you can use : http://4bits.dk/Uwg09z |
| 64 |
|
| 65 |
|
| 66 |
== Screenshots == |
| 67 |
|
| 68 |
1. The enhanced log-in box. |
| 69 |
2. Google Authenticator section on the Profile and Personal options page. |
| 70 |
3. QR code on the Profile and Personal options page. |
| 71 |
4. Google Authenticator app on Android |
| 72 |
|
| 73 |
== Changelog == |
| 74 |
|
| 75 |
= 0.44 = |
| 76 |
* Installation/FAQ section updated. |
| 77 |
* Simplified Chinese translation by Kaijia Feng added. |
| 78 |
* Tabindex on loginpage removed, no longer needed, was used by older WordPress installations. |
| 79 |
* Inputfield renamed to "googleotp". |
| 80 |
* Defaultdescription changed to "WordPressBlog" to avoid trouble for iPhone users. |
| 81 |
* Compatibility with Ryan Hellyer's plugin http://geek.ryanhellyer.net/products/deactivate-google-authenticator/ |
| 82 |
* Must enter all 6 code digits. |
| 83 |
|
| 84 |
= 0.43 = |
| 85 |
* It's now possible for an admin to hide the Google Authenticaator settings on a per-user basis. (Feature request by : Skate-O) |
| 86 |
|
| 87 |
= 0.42 = |
| 88 |
* Autocomplete disabled on code input field. (Feature request by : hiphopsmurf) |
| 89 |
|
| 90 |
= 0.41 = |
| 91 |
* Italian translation by Aldo Latino added. |
| 92 |
|
| 93 |
= 0.40 = |
| 94 |
* Bugfix, typo corrected and PHP notices removed. Thanks to Dion Hulse for his patch. |
| 95 |
|
| 96 |
= 0.39 = |
| 97 |
* Bugfix, Description was not saved to WordPress database when updating profile. Thanks to xxdesmus for noticing this. |
| 98 |
|
| 99 |
= 0.38 = |
| 100 |
* Usability fix, input field for codes changed from password to text type. |
| 101 |
|
| 102 |
= 0.37 = |
| 103 |
* The plugin now supports "relaxed mode" when authenticating. If selected, codes from 4 minutes before and 4 minutes after will work. 30 seconds before and after is still the default setting. |
| 104 |
|
| 105 |
= 0.36 = |
| 106 |
* Bugfix, now an App password can only be used for XMLRPC/APP-Request logins. |
| 107 |
|
| 108 |
= 0.35 = |
| 109 |
* Initial WordPress app support added (XMLRPC). |
| 110 |
|
| 111 |
= 0.30 = |
| 112 |
* Code cleanup |
| 113 |
* Changed generation of secret key, to no longer have requirement of SHA256 on the server |
| 114 |
* German translation |
| 115 |
|
| 116 |
= 0.20 = |
| 117 |
* Initial release |
| 118 |
|
| 119 |
== Credits == |
| 120 |
|
| 121 |
Thanks to: |
| 122 |
|
| 123 |
[Tobias B�thge](http://tobias.baethge.com/) for his code rewrite and German translation. |
| 124 |
|
| 125 |
[Pascal de Bruijn](http://blog.pcode.nl/) for his "relaxed mode" idea. |
| 126 |
|
| 127 |
[Daniel Werl](http://technobabbl.es/) for his usability tips. |
| 128 |
|
| 129 |
[Dion Hulse](http://dd32.id.au/) for his bugfixes. |
| 130 |
|
| 131 |
[Aldo Latino](http://profiles.wordpress.org/users/aldolat/) for his Italian translation. |
| 132 |
|
| 133 |
[Kaijia Feng](http://www.kaijia.me/) for his Simplified Chinese translation. |
| 134 |
|
