Skip to content
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

Get Error 500 invalid_grant when trying to Auth in Production Server #731

Closed
quando1910 opened this issue Oct 25, 2018 · 4 comments
Closed
Assignees
Labels
type: question Request for information or clarification. Not an issue.

Comments

@quando1910
Copy link

Hi everyone, please help me solve the problem. My code is work fine in local, it can run google auth, get access token, blabla... However, when I deploy it, I always get the 500 Error
{ Signet::AuthorizationError (Authorization failed.
Server message:
{
"error": "invalid_grant",
"error_description": "Bad Request"
})
I do not know why, trying to fix NTP too. I'm using with Docker.

@JustinBeckwith JustinBeckwith added triage me I really want to be triaged. 🚨 This issue needs some love. labels Oct 25, 2018
@TheRoyalTnetennba
Copy link
Contributor

Could you share how you are initializing authorization? On GCE instances, the googleauth gem will try to use credentials provided by the metadata server if it does not find credentials by other routes.

@TheRoyalTnetennba TheRoyalTnetennba added the type: question Request for information or clarification. Not an issue. label Dec 4, 2018
@JustinBeckwith JustinBeckwith removed 🚨 This issue needs some love. triage me I really want to be triaged. labels Dec 4, 2018
@mejiaro
Copy link

mejiaro commented Dec 16, 2019

Did you ever find a way to fix this?

@mejiaro
Copy link

mejiaro commented Dec 20, 2019

btw, in case anyone has this problem again, we ended up implementing a strategy around this:

https://github.com/google/google-id-token

@fhinkel fhinkel self-assigned this Dec 8, 2020
@fhinkel
Copy link

fhinkel commented Dec 8, 2020

Greetings, we're closing this. Looks like the issue got resolved. Please let us know if the issue needs to be reopened.

@fhinkel fhinkel closed this as completed Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

5 participants