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

Missing "Login failed" message when two factor app enabled #32654

Closed
PVince81 opened this issue Sep 10, 2018 · 3 comments · Fixed by #33919
Closed

Missing "Login failed" message when two factor app enabled #32654

PVince81 opened this issue Sep 10, 2018 · 3 comments · Fixed by #33919
Assignees
Milestone

Comments

@PVince81
Copy link
Contributor

Steps

  1. Setup 10.0.10 RC1
  2. Install and enable the dummy two factor app "twofactor_email"
  3. Setup a new desktop client and enter valid credentials
  4. The desktop client receives an error and "PasswordLoginForbidden" exception is logged
  5. Check the logs for "Login failed" entries

Expected

One "Login failed" entry per PasswordLoginException entry.

Actual

No "Login failed".

Note: this message is usually used in fail2ban to detect failed login.
It was reported before that we wanted to have it in such scenarios, see #31909 for the "enforce token login" case where we added that.

Version

ownCloud 10.0.10 RC1

@DeepDiver1975 @cdamken

@ownclouders
Copy link
Contributor

GitMate.io thinks possibly related issues are #31465 (Missing symfony event for failed login attempt), #18014 (Failed to login), #20659 (Missing singlequote for login failed log entry), #14232 (Enabling activity app fails), and #28070 (enable apps failed).

@PVince81 PVince81 modified the milestones: QA, backlog Sep 25, 2018
@PVince81
Copy link
Contributor Author

something for @karakayasemi maybe ?

@karakayasemi
Copy link
Contributor

👍 I will look at it.

@karakayasemi karakayasemi self-assigned this Dec 17, 2018
@PVince81 PVince81 modified the milestones: backlog, development Dec 17, 2018
@PVince81 PVince81 modified the milestones: development, QA Jan 11, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jan 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants