🛠️ [TASK] : Keeping Session Cached

[damian-molinski]

Summary

Keychain unlock state should be kept cached as well as User data.

Description

Part of #1255

Reasoning

When user is switching pages via browser url app is restarted and in memory data is lost. This means when user unlocks keychain and switching pages via url or comes back to page after some time keychain should be unlocked.

Another part is keeping user data cached locally. For some time we'll not have information's about user from cat_gateway but we want user to be able to use app, just without any backend interactions.

Requirements

• Keeping keychain unlock state locally. State should be valid base on dynamic config duration before unlock factor have to be given again. Follow in 🛠️ [TASK] : Dynamic frontend config #1348
• Auto refreshing keychain unlock state expirationDate while user is active.
• 🛠️ [TASK] : Writing / Deleting user data after registration is posted. #1382
• 🛠️ [TASK] : User has flag indicating wheter is registration temporary (?). eg. backend does not know about it #1383

Depends on

• 🛠️ [TASK] : Dynamic frontend config #1348

[damian-molinski]

@stevenj or @mike-mcnulty update ticket with how long do we want to keep session valid locally before requiring LockFactor again from user.

[damian-molinski]

Waiting for backend to finish this