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
Google authentication issue #18
Comments
Investigating further I see that the client_id is undefined in Oauth2.js line 28 This is where I log:
This is my output:
|
#Update
But now I face this error:
|
Grant doesn't use |
@simov - thanks for the update. Just out of curiosity, does grant work by reading generic keys like "secret" and formatting to the correct URL according to the provider? I am going through the source and am very keen to understand. Thank you so much. |
Yes. Now that I'm seeing how you configure it, I should enable the Btw you need just this configuration, you don't have to specify all of the parameters by yourself. "google": {
"key":"39009029743-veaeooi4v9ooirabeseujn8u2ohjbqf7.apps.googleusercontent.com",
"secret": "...",
"state":"xxs",
"access_type":"offline",
"scope":["profile","email"],
"callback": "/users"
} |
@simov Thanks for the update. I have got it to work at my end as well. Here is my configuration (probably full of redundancies):
and this is the response:
Curiously, I had to re-fresh the secret to get it to work. Thanks for the help. EDIT: |
No problem. Thanks for the feedback on how you got it working. As I said, to prevent further annoyances, I'll add the original keys for key and secret in the next release. Closing 👍 |
I am using Grant for OAuth2 authentication with google in my express app. I supplied all the parameters in the config.json :
But it still refuses to send all the parameters. I get a "client_id" not sent error:
I modified the library to print out the URL and this is indeed the case:
I did manage to get the first step to work once, by some permutation, but then it failed on client_secret not found.
Is there something I am doing wrong? The library seems to be non buggy.
The text was updated successfully, but these errors were encountered: