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

FEAT: Protect Routing #9

Closed
10 tasks done
nikita-remeslov opened this issue Aug 16, 2024 · 2 comments · Fixed by #19
Closed
10 tasks done

FEAT: Protect Routing #9

nikita-remeslov opened this issue Aug 16, 2024 · 2 comments · Fixed by #19
Assignees
Labels
AC Feature has acceptance criteria FE Fronted feature

Comments

@nikita-remeslov
Copy link
Collaborator

nikita-remeslov commented Aug 16, 2024

What feature?

  • Create ProtectedRoute component
  • Redirect unauthorized users from protected pages to the Sign In page

Add screenshots

No response

Acceptance criteria

  • Ensure that unauthorized users are redirected from protected pages to the Sign In page
  • Ensure that authorized users can successfully access protected routes without any issues
  • Ensure that the system correctly handles expired tokens and redirects users to the Sign In page
  • Ensure that that revoking a token prevents the user from accessing protected routes
  • Ensure that the system displays appropriate error messages when unauthorized users attempt to access protected routes
  • Ensure that logging out a user revokes their tokens and prevents them from accessing protected routes
  • Ensure that refreshing the browser while logged in doesn't require the user to re-authenticate
  • Ensure that that accessing protected routes from multiple tabs or windows works as expected

Testing documentation

https://docs.google.com/spreadsheets/d/1Dn7B49WQK0oi5bE3dmx_Ay1TH0Y1p3QUNDn3VvKWH0o/edit?gid=1927397104#gid=1927397104

@nikita-remeslov nikita-remeslov added the FE Fronted feature label Aug 16, 2024
@nikita-remeslov nikita-remeslov added this to the Release 1.0 milestone Aug 16, 2024
@XCODE89 XCODE89 self-assigned this Aug 19, 2024
@XCODE89 XCODE89 linked a pull request Aug 19, 2024 that will close this issue
@nikita-remeslov nikita-remeslov moved this from Peer Review to In Progress in bsa-2024-outreachvids Aug 21, 2024
@nikita-remeslov nikita-remeslov added MERGE CONFLICTS Merge conflicts while merging the PR and removed MERGE CONFLICTS Merge conflicts while merging the PR labels Aug 21, 2024
@github-project-automation github-project-automation bot moved this from Peer Review to Testing in bsa-2024-outreachvids Aug 23, 2024
@alien513
Copy link
Collaborator

This component does not perform any actions yet and allows access to all routes until user persistence is implemented. Pending.

@alien513 alien513 added the QA QA tasks label Sep 1, 2024
@alien513 alien513 added the AC Feature has acceptance criteria label Sep 9, 2024
@alien513
Copy link
Collaborator

alien513 commented Sep 9, 2024

Bugs created: #210, #213
Bugs should be resolved in the following fix: #187

@alien513 alien513 removed the QA QA tasks label Sep 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AC Feature has acceptance criteria FE Fronted feature
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants