-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
OpenIdException(invalid_grant): Invalid JWT Signature in 0.1.3 #7
Comments
can you post the stack trace and example code that throws this? |
Hello, I have the same problem. Here's some example code:
The reply from the token endpoint (https://oauth2.googleapis.com/token) : The credentials are loaded from Also maybe a related issue : exchanging a custom token for an ID and refresh token doesn't work for me (https://firebase.google.com/docs/reference/rest/auth#section-verify-custom-token) Sending a token obtained from |
I updated my service account this time with a key generated from the Firebase console instead of the Cloud Console , now everything works. |
Sorry for the delay in replying. My code same as in your example code. I have tried with
Here is the terminal error
|
Hey, it works now for me.
But I wanted to try the other way round. I created the service key from the Cloud Console instead of Firebase Console and it worked for me. Yahooooo! |
@akfaisel What was the change you made if any? I'm trying to generate a key from Cloud Console since I'm also using the googleapis package to use Cloud Tasks, so I need additional permissions beyond the firebase admin sdk. |
This appears to happen with certain keys (maybe some character that's not parsed properly?). One workaround is to just generate keys until it works. |
It looks like we're also being affected by this issue. Will try what @bedardjo has suggested and regenerate the keys. The existing cert is definitely valid as it works to access firestore via a different package. |
Hi
Thank you for fixing state validation error.
Unfortunately, there is a new error coming from the new version 0.1.3 and error is given below.
I have done the following.
The text was updated successfully, but these errors were encountered: