Optimize JWT token refresh app-frontend

[jezpoz]

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

• Is this issue labeled with a correct area label?
• QA has been done

[HanneLauritsen1967]

@jezpoz hei er det du i tamagotchi som jobber med denne? Siste issues for epic 1304

[matsgm]

Look at Adal from Microsoft for tips on refreshing.

[jezpoz]

I was thinking that this could be a specification with UX and technical. Since we need to know what should classify as a user begin active. And also use the time to come up with a better technological solution for this, since some of the developers did not like the implementation of this. (Not mentioning any by name, isn't that right @lorang92? 😂)