Sync does not work after user is inactive for some time

[sleidig]

Describe the bug
The remote authentication is not refreshed automatically so if a user is not making changes for 10 minutes, the remote session expires. Any local changes after that are not synced (Network tab of developer console will show a 401 response).

To Reproduce
Steps to reproduce the behavior:

1. Log in
2. Edit an entity --> changes are synced as expected
3. Wait 10 minutes
4. Edit another entity --> changes are not synced to server, request receives 401

Expected behavior
As long as the user is logged in the frontend, the remote auth should be automatically kept alive so that syncing always works.

[TheSlimvReal]

with #956 this will be somewhat fixes by our own auth implementation (logged in for 2h, for each requests during that time the two hours start again). What is missing is a frontend feedback when the auth-cookie is expired. In this case the user should be logged out.

[TheSlimvReal]

One option could be to automatically logout the user if the cookie expires / requests of the PouchDB are returning 401. This should not restrict the offline capability though.

[sleidig]

also see related #2044

[aam-digital-ci]

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

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 📦🚀