diff options
| author | Christoph Wurst <christoph@winzerhof-wurst.at> | 2022-11-07 15:08:48 +0100 |
|---|---|---|
| committer | Christoph Wurst <christoph@winzerhof-wurst.at> | 2022-11-07 15:08:48 +0100 |
| commit | e2d3409a34e5d7a58fc653f26a480294fc6eeaa7 (patch) | |
| tree | 872537c86a9c91884409f77419c3dd906413e35f | |
| parent | f5181f36828c9407f7e5fd4ca5cad27ed2baf88c (diff) | |
| download | nextcloud-server-e2d3409a34e5d7a58fc653f26a480294fc6eeaa7.tar.gz nextcloud-server-e2d3409a34e5d7a58fc653f26a480294fc6eeaa7.zip | |
Fix unsuccessful token login logged as error
The condition of a non-existent login token can happen for concurrent
requests. Admins can not do anything about this. So this is to be
expected to happen occasionally. This event is only bad if none of the
requests is able to re-acquire a session. Luckily this happens rarely.
If a login loop persists an admin can still lower the log level to find
this info. But a default error log level will no longer write those
infos about the failed cookie login of one request.
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
| -rw-r--r-- | lib/private/User/Session.php | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/private/User/Session.php b/lib/private/User/Session.php index 5117812db31..acf95b1e271 100644 --- a/lib/private/User/Session.php +++ b/lib/private/User/Session.php @@ -868,7 +868,7 @@ class Session implements IUserSession, Emitter { $tokens = $this->config->getUserKeys($uid, 'login_token'); // test cookies token against stored tokens if (!in_array($currentToken, $tokens, true)) { - $this->logger->error('Tried to log in {uid} but could not verify token', [ + $this->logger->info('Tried to log in {uid} but could not verify token', [ 'app' => 'core', 'uid' => $uid, ]); |