fix(node-ui): expired client key #939
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
frdomovic
requested review from
xilosada,
chefsale,
alenmestrov and
MatejVukosav
MatejVukosav
approved these changes
Nov 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix(node-ui): expired client key
Summary
Axios interceptor for all calls that checks if user is authorized (if no returns 401). If status is 401 it redirects user to setup page to setup again node url + login.
This can be recreated by init + setup node + run admin dashboard login. Then delete node data and recreate the steps.
The page will have in local storage items that tell the page thats its authorized but requests are not authorized as storage client key does not match the server one.
Test plan
Screen.Recording.2024-11-05.at.11.17.18.mov