Christoph Wurst e2d3409a34 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>		2022-11-07 15:08:48 +07:00
..
Listeners	Fix avatar cleanup on user delete	2022-09-19 21:36:50 +07:00
Backend.php	Update php licenses	2021-06-04 22:02:41 +07:00
Database.php	Fix creation of new user and display the correct error message	2022-08-22 19:13:11 +07:00
DisplayNameCache.php	Make DisplayNameCache return null if user doesn't exists	2022-08-16 14:10:05 +07:00
LazyUser.php	Make DisplayNameCache return null if user doesn't exists	2022-08-16 14:10:05 +07:00
LoginException.php	Update php licenses	2021-06-04 22:02:41 +07:00
Manager.php	LDAP to no register new users when outside of fair use or over limits	2022-10-18 12:57:43 +07:00
NoUserException.php	Update php licenses	2021-06-04 22:02:41 +07:00
Session.php	Fix unsuccessful token login logged as error	2022-11-07 15:08:48 +07:00
User.php	Merge pull request #33793 from nextcloud/fix/noid/rtrim-cloud-id	2022-09-15 10:46:39 +07:00