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