Skip to content

Conversation

@backportbot-nextcloud
Copy link

backport of #35007

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 <[email protected]>
@szaimen szaimen enabled auto-merge November 7, 2022 16:43
@ChristophWurst ChristophWurst added the 4. to release Ready to be released and/or waiting for tests to finish label Nov 7, 2022
@szaimen
Copy link
Contributor

szaimen commented Nov 7, 2022

drone needs a restart...

@szaimen szaimen disabled auto-merge November 8, 2022 09:50
@szaimen szaimen merged commit 18515f6 into stable25 Nov 8, 2022
@szaimen szaimen deleted the backport/35007/stable25 branch November 8, 2022 09:50
@blizzz blizzz mentioned this pull request Nov 21, 2022
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to release Ready to be released and/or waiting for tests to finish bug feature: authentication

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants