Description
JWT-token refresh in app-frontend is implemented in a way that it uses "alot" of CPU resources. On a fairly new macbook it jumps from 0.3% (idle) to 3% load when moving the mouse. The increased usage of CPU could be noticeable on a "weaker" pc.
A suggested solution is that we do how netbanks handles sessions, where a little notification shows up a little while before the token expires. It should say something like "Your session is expiring soon, do you want to keep working?" and have an ok-button.
In scope
- How long is the token valid?
- What must a user do to be classified as active?
- How often should we refresh the token?
- How do we implement the checks if the token should be active?
Constraints
Analysis
Conclusion
Short summary of the proposed solution.
Tasks
Description
JWT-token refresh in app-frontend is implemented in a way that it uses "alot" of CPU resources. On a fairly new macbook it jumps from 0.3% (idle) to 3% load when moving the mouse. The increased usage of CPU could be noticeable on a "weaker" pc.
A suggested solution is that we do how netbanks handles sessions, where a little notification shows up a little while before the token expires. It should say something like "Your session is expiring soon, do you want to keep working?" and have an ok-button.
In scope
Constraints
Analysis
Conclusion
Tasks