-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
v9 Typing breaks existing refresh tokens #1435
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think the typing stuff in v9 has broken compatibility with my existing refresh tokens.
Ive just updated to v9 and I was able to add all the types to my classes and everything seems to be working fine. I can create new tokens via auth code or device code and via refresh.
However when I try to use an existing refresh token to get a new access token it fails with the following error:
I believe this is because my userid used to be an integer. Ive changed anywhere that I pass the user id into the system to convert it to a string so its working for new stuff but existing tokens contain the id as an int.
Since the refresh token is handled inside the library I dont think theres anywhere I can change my code to convert it before creating the new token.
It looks like when respondToAccessTokenRequest in RefreshTokenGrant reads the old refresh token info it would need to convert it to string before calling issueAccessToken.
Thanks.
btw. The Device Code support is great I've been waiting for that! Cheers!
The text was updated successfully, but these errors were encountered: