Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable24] Fix unsuccessful token login logged as error #35012

Merged
merged 1 commit into from
Nov 8, 2022

Conversation

backportbot-nextcloud[bot]
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 <christoph@winzerhof-wurst.at>
@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 to get restarted...

@szaimen szaimen merged commit e9e248d into stable24 Nov 8, 2022
@szaimen szaimen deleted the backport/35007/stable24 branch November 8, 2022 09:50
@blizzz blizzz mentioned this pull request Nov 21, 2022
9 tasks
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.

2 participants