-
Notifications
You must be signed in to change notification settings - Fork 53
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
refreshToken has stopped working due to changes in JWT #167
Comments
SlyDave
changed the title
refreshToken has stopped working due to changesin JWT
refreshToken has stopped working due to changes in JWT
Aug 11, 2023
passport v11 and oauth2-server v8 both updated to support jtw 5.0 which removed the method being called. lighthouse-graphql-passport-auth has support for passport v11, even though it specifies jtw 4.0 so we've got an old-fashioned dependency break :D
|
A quick for for this was committed in #166 - This buys some time. but doesn't resolve the underlying issue |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like something has changed somewhere? RefreshToken is crashing out with an error because it's trying to call
forUnsecuredSigner()
which no longer appears to exist in the JWT package being used.Found some notes about it in the JWT docs: https://lcobucci-jwt.readthedocs.io/en/stable/upgrading/#removal-of-none-algorithm
Appears to be due to the none-algorithm being removed,
The text was updated successfully, but these errors were encountered: