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>

diff --git a/lib/private/User/Session.php b/lib/private/User/Session.php
index 302f6174bc913f5cfc611a8f5693db3511975e4a..522adaf112973c2919ae53d2b022afa4e05daf7e 100644 (file)
--- 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,
                        ]);