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

JWT Auth #135

Open
5 tasks
v0ldemar01 opened this issue Jun 11, 2024 · 0 comments
Open
5 tasks

JWT Auth #135

v0ldemar01 opened this issue Jun 11, 2024 · 0 comments

Comments

@v0ldemar01
Copy link
Collaborator

v0ldemar01 commented Jun 11, 2024

User story:
As a user, I want to stay logged in when I revisit the app later so that I don’t have to enter my credentials every time.

Acceptance Criteria:

  • If a user successfully signed up and his account is created then a unique JWT Verification token should be generated.
  • If the user sign in and the user’s account credentials are verified, then a unique JWT Authorization token should be Implement for the user’s session.
  • The token should be passed to the frontend and stored in the local Storage.
  • The JWT token should store the user’s id.
  • The token should have an expiration time - one day. The token should become invalid and unusable after the expiration time.
@v0ldemar01 v0ldemar01 changed the title Protected routing JWT Auth Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant