Owncloud client asks me for authentication after every network change

[macz]

Expected behaviour

After I authorise desktop client it should stay authorized untill I logout or reinstall client.

Actual behaviour

Mac OS X desktop client asks me to authorize every account (have more than one) again and again whenever I change the network I’m connected to.

Steps to reproduce

1. Connect new account to desktop client
2. Login to account in web browser
3. Provide 2FA code (TOTP turned on for account)
4. After few hours change the network you are connected to Desktop client opens web browser auth window for every account or some of them requesting authorization and providing 2FA again

Server configuration

Operating system:
CentOS Linux release 7.9.2009 (Core)
Web server:
Server version: Apache/2.4.6 (CentOS)
Server built: Mar 24 2022 14:57:57
Database:
mysql Ver 15.1 Distrib 5.5.68-MariaDB, for Linux (x86_64) using readline 5.1
PHP version:
PHP 7.3.33 (cli) (built: Nov 16 2021 11:18:28) ( NTS )
ownCloud version:
version | 10.7.0.4
versionstring | 10.7.0
edition | Community
Storage backend (external storage):

Client configuration

Client version:
2.10.1. (build 7187)
Operating system:
System Version: macOS 12.2.1 (21D62)
Kernel Version: Darwin 21.3.0
OS language:
English
Qt version used by client package (Linux only, see also Settings dialog):

Client package (From ownCloud or distro) (Linux only):

Installation path of client:
default

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer
logs.

Template for output < 10 lines

1. Client logfile: Output of owncloud --logwindow or owncloud --logfile log.txt
   (On Windows using cmd.exe, you might need to first cd into the ownCloud directory)
   (See also Redirect Notice )

2. Web server error log:

3. Server logfile: ownCloud log (data/owncloud.log):

[fmoc]

Looks like a server configuration issue. I can’t tell for sure without a log excerpt, but as far as I can see, the server rejects the issued OAuth2 token once the client tries to use it. Could be caused by a timeout setting on the server, some oversensitive security extension (which denies access on IP changes), etc.

Please provide a log excerpt.