App should request re-login if authentication expired / fails in background

[sleidig]

We have a few bugs users experience from time to time which are related to the authentication of a user expiring in the app. Currently we do not explicitly handle such cases when a 401 error occurs:

• Sync does not work after user is inactive for some time #935
• User roles sometimes not accessible because auth with backend expired #2044
• this also has caused a file attachment upload to fail for a user

Tasks for implementation (to be discussed):

• Detect when the current access token expires and automatically get a new one using the refresh token
• (if still necessary) Catch 401 errors and send people to login screen if the reason is an expired login (or show a popup: "Continue offline or login again?")
• use overall interceptor in Angular to detect these errors? (and check if some are handled automtically because the refresh token then gets a new valid token)

[sleidig]

Related errors (in Sentry):

• No token received from Keycloak (after seeing 401 request failures to /db) 1
• Errors during HTTP requests for sync bubble up into various error logs (e.g. "Unexpected end of JSON input", "string did not match the expected pattern", "unexpected token '<' is not valid JSON") 1 2 3

[aam-digital-ci]

🎉 This issue has been resolved in version 3.34.0-master.6 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[aam-digital-ci]

🎉 This issue has been resolved in version 3.34.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀