Skip to content
This repository has been archived by the owner on Jun 27, 2019. It is now read-only.

zapier login fails to authenticate Google login credentials #402

Closed
akflaherty opened this issue Feb 21, 2019 · 5 comments
Closed

zapier login fails to authenticate Google login credentials #402

akflaherty opened this issue Feb 21, 2019 · 5 comments

Comments

@akflaherty
Copy link

If a user account was created by signing in to Google, then entering that email address and password will not work with zapier login.
The following error is returned:

Error! "https://zapier.com/api/platform/cli/keys" returned "401" saying "Could not authenticate you."

What would you like to change?

Add a command line argument to zapier login, to generate the zapierrc file for Google accounts

Your Environment

  • CLI Version (zapier -v): 7.6.1
  • Operating System: Windows 10
  • Node.js Version: 8.11.4

I was able to successfully log in with an account generated directly through Zapier with a username and password.

@eliangcs
Copy link
Member

@akflaherty when you signed up Zapier with your Google account, we generated a random password for your Zapier account. You and we can never retrieve that random password, so you need to reset it from https://zapier.com/app/login/forgot and use that password in zapier login. Let us know if it still doesn't work.

@xavdid
Copy link
Contributor

xavdid commented Feb 21, 2019

That is to say, this is working as intended (albeit unclear). Accounts created purely through google have no password. To use the CLI, you need to create a password via a password reset (as mentioned above) and then you'll be able to log in.

We should definitely document this more clearly though!

@jbaranski
Copy link

I ran into the same problem. It's not clear until reading this.

@xavdid
Copy link
Contributor

xavdid commented Apr 3, 2019

Sorry about that! We've got work scheduled to resolve this in the next version. Thanks for your patience!

@xavdid
Copy link
Contributor

xavdid commented May 20, 2019

8.1.0 gives a warning about this and #420 (unreleased, but coming soon-ish) has similar messaging (and an eventual workaround). Going to go ahead and close.

Thanks for the report!

@xavdid xavdid closed this as completed May 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants