Google 2-step verification for WordPress : Guide

Google 2-step verification for WordPress can be implemented just like Google’s own hosted sign in pages for self hosted WordPress by using API or simply plugin. Google 2-step verification for WordPress with SSL can definitely make your WordPress login quite strong. Unlike older methods to secure WordPress login with limiting the number of login attempts for preventing brute force attacks, Google 2-step verification for WordPress makes somewhat warranted and quantifiable security especially when combined with SSL.

Google 2-step verification for WordPress : API based core guide

Google 2-step verification for WordPress is a bit complicated than any other API simply because it is dependent on mobile carrier. You will get all the information about Google 2-step verification here :

If you are just an WordPress user who needs extra security, you need to read this current paragraph, simply move to the next paragraph. SSL is not mandatory factor for implementing Google 2-step verification for WordPress. Not all countries support mobile phone system that can receive the verification code via text message or phone call. That list is given on the above mentioned web page of Google. If you are not sure whether will work or not with SSL for your setup, you can use a free SSL certificate as described in our Installing Free SSL Certificate for Rackspace Cloud Server guide. For Rackspace Cloud Sites you need to follow this guide. The best practice is to use Extended Validation SSL Certificate for very sensitive domain with wild card subdomain support, redirecting  wp-login.php with CNAME to some subdomain looking webpage. The redirection for WordPress should be tweaked properly, otherwise the user will fail to login.

Google 2-step verification for WordPress : How it works

The basic login of WordPress is fully dependent on MySQL Database. If the PHP of main server or database server (in case of scalable Cloud setup) fails to work, which can happen during an upgrade, if Apache2 (for typical LAMP server setup) does not work rightly, wp-config can be opened like a text file. It is quite rare with even a setup by a novice, but the risk is present.  Practically there is  no need to know hacking, people frankly can access your wp-config.php in browser. It can happen with debugging mode too.

The basic process  is to involve  Google Authenticator :

If you want to setup Google 2-step verification for WordPress yourself, you can check the mobile setup part :

Google 2-step verification for WordPress : Existing Google 2-step verification Plugins

There are two plugins (at the time of writing) that enables Google 2-step verification for WordPress :

Unfortunately, both of these Google 2-step verification for WordPress Plugin are just basic and does not work for advanced EV SSL with CNAME redirection out of the box.

Google 2-step verification for WordPress : The Postulated Ideal Setup

The ideal setup for fully secured setup for Google 2-step verification for WordPress should be :

• No real wp-login.php on the main WordPress domain. There would be a fake HTML webpage with Javascript to track the user.  The page should not load if the hacker disables JavaScript.  The username in WordPress is quite easy to discover from frontend and needs no special knowledge. We are not describing the method – you will definitely apply it on our site ! It will, indeed a Guru Killer. We are taking that the hacker discovered the username and used Brute Force or just guess based on logics. Whatever the password the user types it must redirect to a fake WordPress wp-admin to trap the hacker.
• If you website is wordpress-site.com, you  login page should be like for https://login.wordpress-site.com with a session  :

• After giving proper input, it would point towards the https version of wp-admin.
• In between these two, Google 2-step verification process will work, asking Google Server for the proper match.

Google 2-step verification for WordPress : Disadvantages

Google 2-step verification for WordPress in any method is fully dependent on Google’s server and the device.