Open jwulf opened 7 years ago
When I step through their wizard and say that I'm looking for credentials to allow a web browser || web server access a user's data via the Google+ API, it tells me that I have credentials already for both of those scenarios.
When I use either of those credentials with watchmen, Google gives me a 401 error, with the client key on the screen, like this:
401. That’s an error.
Error: invalid_client
The OAuth client was not found.
Request Details
response_type=code
redirect_uri=http://watcher.magikcraft.io/auth/google/callback
scope=https://www.google.com/m8/feeds https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/userinfo.profile
client_id='672769544416-45vu7vkkqtqbpv1p1ompcfjrt9smgmpv.apps.googleusercontent.com'
That’s all we know.
Same problem here, @jwulf have you found a solution?
Here's a rough guide based on what I did to get it working:
That should get you the Client ID and the Client Secret to put in the config files. I also added a Google Analytics ID to the config files, which you can get from a Google Analytics account
Couple of thoughts:
For me it was necessary to remove all quotes in env file, so it will be just:
WATCHMEN_BASE_URL=http://localhost:3000 WATCHMEN_WEB_PORT=3000 ...
as well as Google keys. Otherwise this quotes remains in auth query and it will fail.
There are deprecated options
scope: 'https://www.google.com/m8/feeds https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/userinfo.profile'
it needs to be replaced with
scope: 'email profile'
in webserver/routes/web-auth-route.js
You need to enable Google + API in your console otherwise auth will fail (as 0f 2017)
The docs say:
Can you give some more details on this? On Google there are several types of OAuth credentials (web browser / web server || access your data / access users' data) and a bunch of different parameters (origin URL || redirect URL).
I read in another issue that you need to enable the Google+ API, so I did that; then generated a couple of different credentials for OAuth. They all result in an error.