Skip to content

Conversation

@longshuicy
Copy link
Member

  • Add Depends(get_current_user) to each protected route. When session expired, decode_token still works but userinfo will complain about expired signature (suspect related to user session expiration). To unify their behavior, check userinfo
  • Change frontend action to logout user properly when refresh failed.
  • Note don't set the session idle time to a small value. The minimum of those four will decide the life span of refresh token. If set too small this will cause refresh token expiration too soon and can never refresh; and other weird behaviours

image

@longshuicy longshuicy linked an issue Jul 12, 2022 that may be closed by this pull request
@longshuicy longshuicy marked this pull request as ready for review July 13, 2022 15:10
Copy link
Contributor

@tcnichol tcnichol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything seems to work as intended here.

@longshuicy
Copy link
Member Author

Ready to be reviewed again

@longshuicy longshuicy requested a review from lmarini July 20, 2022 17:34
@lmarini lmarini merged commit cb991d2 into main Aug 25, 2022
@lmarini lmarini deleted the 41-random-jwt-signature-verification-failed-error branch August 25, 2022 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

random jwt Signature verification failed error

4 participants