Protect Your Google Apps Login From Phishing Attacks

Following a series of Google Apps login phishing attacks (specifically on Google Docs) in 2017, Google made several improvements. At the time, while we welcomed Google taking steps to address the phishing problems, it caused issues for WordPress plugins.

Specifically, the updates made it challenging in cases where customer installation required individuals to create a Google Cloud project with their own OAuth 2.0 Client IDs.

To make things easier and safer for legitimate users who need to create Google applications, we recommended that Google:

  • Allow users to authenticate against an OAuth ID they created using the same account as the one being used to access the app.
  • Allow admins to whitelist specific ID/Secrets on their domain and also allow any regular Gmail account to whitelist for their own use.
  • Provide a simpler verification form, including clear and consistent wording (is a ‘project ID’ the alphanumeric string, or the integer?), plus no long text fields (‘the app needs calendar scopes in order to access the user’s calendar…’). There is no point checking the privacy policy for the app since it can be changed easily in the future and will presumably not be respected by phishers!
  • Provide a clearer error message where unverified apps encounter ‘Invalid Scope.’
  • Deliver documentation explaining the new verification processes they have rolled out.
  • Offer a more robust and selective solution than joining the ‘Risky’ Group (Google already confirmed to us they are aware this cannot be a permanent solution).

Since then, we have even more suggestions for WordPress users using Google Apps login to deter attackers.


Allowing only some employee Groups to access your WordPress intranet

Many customers use our Google Apps Login Enterprise version to restrict access to their WordPress intranet so that, not only is it inaccessible to non-employees, but certain groups of employees should have different WordPress roles, and perhaps some employees should not have access at all.

Is your WordPress installation secure?

Following the Heartbleed vulnerability affecting all of us on the web, security has been a big topic lately. Some of us even changed our years-old passwords, and maybe enabled 2-factor authentication on our email accounts… (2-factor is the system where you need a code generated by, say, your mobile phone as well as your regular password to login.)

So it seems that most of us survived, but given the wake-up call, we thought it would be a good time to remind you of some simple things you can do to ensure your WordPress installation is secure.

Making the most of WordPress’ user system

How important is it to set up a comprehensive user hierarchy on your WordPress sites?

This article will explain the benefits of creating multiple users for your WordPress site and how understanding the different roles users can have will give you the control needed to allow others to create content, without risking control of the site itself. The article will also teach you to check your site configuration to understand if there are any backdoors that unwanted visitors could use to register, view private content, or make undesired changes to your site.


Google Apps Login is trusted by thousands of organizations from small businesses to NASDAQ-listed companies and government organizations.

Users click their way through Login via Google (just one click after the first time)

Users click their way through Login via Google (just one click after the first time)

You can try it out by clicking below to auto-create a test account on this site! This will show you the basic Google login process.
Try out Google login

Logging in is only the start – Google Apps Login takes care of all your WordPress user management. Find out more here.