-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GoogleOauth2: "Invalid credentials". #44
Comments
Those redirect URIs and origins look exactly like what we have working. But just to double check, do you have those URLs prefixed with And then in your
|
Alright, great. I will double check. Can anyone please help update/verify the following wiki documentation? |
Hm, our settings seem correct, as outlined above. The redirect takes us back to our website, but the message still indicates |
API Umbrella seems to prefer HTTPS by default, and we have not purchased an SSL certificate. Could it be related to us not having a validated SSL certificate? |
Sorry again for the delay. I ran through this setup process on a machine from scratch and updated the auth strategies documentation (thanks again for getting that started). However, I think the instructions mostly match what you had discovered, so I'm a little puzzled why this isn't working for you. Mine also worked with my local machine having a self-signed SSL certificate, so I don't think the SSL stuff should make a difference. Just to verify, your form and confirmation looked like these? And then your web:
admin:
initial_superusers:
- your-email@whatever.com
auth_strategies:
github:
client_id: YOUR_ID
client_secret: YOUR_SECRET
google:
client_id: YOUR_ID.apps.googleusercontent.com
client_secret: YOUR_SECRET Assuming that all looks correct, is there anything in the |
I have double and triple checked the settings, and even re-created the Client ID. I have tried with and without trailing slashes. Could this be related to HTTPS (i.e. we do not have an HTTPS certificate for the domain)? |
D'oh! I think I just realized what the issue is. The omniauth-google-oauth2 strategy recently made some changes that require you enable the "Contacts API" and "Google+ API" services in the API console:
I totally forgot that this recently bit us too after we upgraded omniauth-google-oauth2 (but since you only have to do this once, I had forgotten). Very sorry for not realizing this sooner, but hopefully this explains things and makes things work for you (finally!). I've updated our own documentation, but let me know if that does the trick or not. |
@brylie Just curious and wanted to follow up: Did you have a chance to see if my last comment about enabling the "Contacts API" and "Google+ API" in the Google API console fixed things for you? |
I get similar error with all APIs mentioned enabled. Same client ID and secret are working with another oauth2 app. |
When configuring the Google settings for API Umbrella, I get the following error:
The user email address is in the initial_superusers list, and the Google settings for
client_id
andclient_secret
seem correct.On the Google configuration end of things, what should I put for:
I currently have:
The text was updated successfully, but these errors were encountered: