Skip to content
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

Add tests for reading userId and JWT payload from the frontend #11

Open
6 of 10 tasks
rishabhpoddar opened this issue Sep 15, 2020 · 0 comments
Open
6 of 10 tasks

Comments

@rishabhpoddar
Copy link
Contributor

rishabhpoddar commented Sep 15, 2020

  • Create a session check that userId is there on the frontend
  • Refresh a session and make sure JWT payload is accessible
  • Access the JWT payload when the access token is expired and make sure that refresh is called once - this test is commented "refresh session via reading of frontend info".
  • When the session is removed, check that the front-token is also removed
  • Update JWT payload and check that frontend token is also updated
  • Create a session with some custom JWT payload, and see if that's accessible on the frontend
  • Changing on jwt payload with blacklisting on, reflects the change immediately vs with refresh, it only reflects after a refresh call
  • Resolve TODO from test "test session should not exist when user calls log out" and "test with fetch session should not exist when user calls log out".
  • Uncomment "refresh session via reading of frontend info" and "refresh session via reading of frontend info using fetch"
  • Resolve TODOs in "update jwt data" and "test update jwt data with fetch", after all drivers have implementation.
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

No branches or pull requests

1 participant