View the original community article here
Last Tested: Oct 24, 2019
This basically means that Google Auth is failing to log in that user for one reason or another. Try and figure out whether it is happening to all users or just one user.
In summary, If a single user cannot log in:
-
Have the user that can't log in check that their GSuite name matches their user name
-
Ensure the email domain is listed in the admin > google domain list (ex: looker.com, google.com)
-
Check that the user hasn't blocked the looker application on their google chrome account (more on how to navigate to that here)
-
Check if the user is logged into G+ and make sure they have a first and last name there. (Google Auth will check the user's G+ account first.)
If it is just one user, this is generally because the user is missing either a first or last name. You can verify in the logs for this by checking for something like: [WARN|18a53|google] :: User authentication failed: User info is missing first or last name
Sometimes the GSuite Admin from the customers still see the user account with both first name and last name, however users have changed their account name by themselves with only first name or last name. To avoid this issue happening again, GSuite Admins can switch off "Allow users to customize this setting".
A single user may have also revoked third party access from looker on their user account. In order to double check if this is the case, have that user navigate to the list of Third-party apps with account access in their google profile:
-
Go to your Google Account.
-
On the left navigation panel, select Security.
-
On the Third-party apps with account access panel, select Manage third-party access.
-
Select the site or app you want to remove.
-
Select Remove Access.
This content is subject to limited support.