mirror of
https://github.com/EddieTheCubeHead/Stagnum.git
synced 2026-04-26 14:15:50 +03:00
[GH-ISSUE #242] Client is unusable due to token changes #146
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#146
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 (Apr 14, 2024).
Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/242
No matter what core returns to the token check client doesn't redirect to login. Thus erroring requests (no token, invalid token) also don't force login. Only way to use client at the moment is to navigate to the login page manually.
Make it so erroring requests in token check force relogin.
@OttoAhlfors commented on GitHub (Apr 15, 2024):
Redirection works for me on master. I can look into this further but somenone needs to show me what the issue is
@EddieTheCubeHead commented on GitHub (Apr 15, 2024):
For me, this reproduced running with docker compose in Master. Maybe that helps?
@OttoAhlfors commented on GitHub (Apr 15, 2024):
Even with docker its working as it should
@EddieTheCubeHead commented on GitHub (Apr 15, 2024):
Then feel free to close as works as expected 👍
@OttoAhlfors commented on GitHub (Apr 15, 2024):
Okay there were some changes I had not pulled and now its busted, will start to work on a fix
@EddieTheCubeHead commented on GitHub (Apr 15, 2024):
Luckily I think the fix should be simple. If you just check return code >= 400 and reroute those to login it should work(?)
@OttoAhlfors commented on GitHub (Apr 15, 2024):
I am getting some cors errors okay these were caused by someone switching backend ports
@OttoAhlfors commented on GitHub (Apr 15, 2024):
I dont think thats the issue the if else check that should reroute the user when code and state arent defined is workign as it should, for some reason the actual redirect fuction isnt working
@OttoAhlfors commented on GitHub (Apr 15, 2024):
Fix has been found, there seems to be an issue with redirect and .catch() dont know why it did not come up earlier changing redirect() to router.push() seems to work