Oauth2 failing to get new token. #22
Unanswered
hugoprudente
asked this question in
Q&A
Replies: 1 comment
-
Same happens to me. The complete detailed error in the HTTP response is the following: {
"error": "invalid_grant",
"message": "The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.",
"hint": "Failed to verify `code_verifier`."
} Everything seems to be correct in the request according to the API specification and the unofficial guide. Adding the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team,
I think something changed on the MAL backend, I use windows to generate the token for my containers as they don't have browser and last time that I logged was fine but now I have 400 invalid_request what is quite weird.
Any ideas?
If opening url failed enter it manually into your browser:
Paste url you were redirected to
If I remove the "redirect_uri" I have the following error.
With that the
client.refresh_bearer_token()
works. But.Beta Was this translation helpful? Give feedback.
All reactions