The client should not simply invalidate oauth tokens, even if it receives a timeout or keepassxc is close; it should instead again try to use the token then when the db is reopened as an alternative.
Actual behaviour
Valid oauth tokens are trashed, browser windows / tab opens and re-authentication is required.
Steps to reproduce
setup owncloud to use secretservice via keepassxc
use owncloud
at some point that I cannot exactly grasp (it does not always happen after data base is closed; I believe it happens regularly if keepassxc is not running before owncloud-client, keepassxc is closed, or after the computer returns from sleep), the oauth token is attempted to be trashed. However, 1. trashing valid oauth tokens should never be required in the first place and 2. this does not work automatically if saving the data base requires yubikey interaction. This is totally annoying.
Server configuration
owncloud enterprise, no further information available
Client configuration
Client version: 2.9.2
Operating system: archlinux
OS language: en
Qt version used by client package (Linux only, see also Settings dialog): -
Client package (From ownCloud or distro) (Linux only): owncloud-client
Expected behaviour
The client should not simply invalidate oauth tokens, even if it receives a timeout or keepassxc is close; it should instead again try to use the token then when the db is reopened as an alternative.
Actual behaviour
Valid oauth tokens are trashed, browser windows / tab opens and re-authentication is required.
Steps to reproduce
Server configuration
owncloud enterprise, no further information available
Client configuration
Client version: 2.9.2 Operating system: archlinux OS language: en Qt version used by client package (Linux only, see also Settings dialog): - Client package (From ownCloud or distro) (Linux only): owncloud-client
Logs
Client logfile