mirror of
https://github.com/EddieTheCubeHead/Stagnum.git
synced 2026-04-26 22:25:52 +03:00
[GH-ISSUE #49] Implement login and token functionality to frontend #40
Labels
No labels
bug
bug
client
design
documentation
feature
feature
infrastructure
pull-request
ready for development
server
server
spike
technical work
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Stagnum#40
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @EddieTheCubeHead on GitHub (Jan 29, 2024).
Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/49
If client doesn't have a token, home page (all routes? If possible) should reroute to login page.
Once client gets token from login page, all requests should include the token in header "token"
Acceptance criteria: described functionality exists and is tested accoding to front end team standards. Test set passes
@tuomasmustakallio commented on GitHub (Jan 30, 2024):
https://jasonwatmore.com/post/2021/08/30/next-js-redirect-to-login-page-if-unauthenticated
This should be a good start for this ticket for the rerouting. We don't need to have the authentication check from the server at the authCeck-function but a simple token != null or something like that for start which then runs on router events.