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> |
1 jaar geleden | |
---|---|---|
.. | ||
Listeners | Fix avatar cleanup on user delete | 1 jaar geleden |
Backend.php | Update php licenses | 3 jaren geleden |
Database.php | Fix creation of new user and display the correct error message | 1 jaar geleden |
DisplayNameCache.php | Make DisplayNameCache return null if user doesn't exists | 1 jaar geleden |
LazyUser.php | Make DisplayNameCache return null if user doesn't exists | 1 jaar geleden |
LoginException.php | Update php licenses | 3 jaren geleden |
Manager.php | LDAP to no register new users when outside of fair use or over limits | 1 jaar geleden |
NoUserException.php | Update php licenses | 3 jaren geleden |
Session.php | Fix unsuccessful token login logged as error | 1 jaar geleden |
User.php | Merge pull request #33793 from nextcloud/fix/noid/rtrim-cloud-id | 1 jaar geleden |