From 05a22831e1489e8684f3290f0109eedfdbad6f9e Mon Sep 17 00:00:00 2001 From: Christoph Wurst Date: Mon, 7 Nov 2022 15:08:48 +0100 Subject: [PATCH] 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 --- lib/private/User/Session.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/private/User/Session.php b/lib/private/User/Session.php index 302f6174bc9..522adaf1129 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, ]); -- 2.39.5