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

Account does not get blocked despite wrong password when using email address for login #528

Open
LM-vb opened this issue Oct 4, 2021 · 4 comments

Comments

@LM-vb
Copy link

LM-vb commented Oct 4, 2021

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. Under Administration/Security/Password Policy: set "Number of login attempts before the user account is blocked" to e.g. 3.
  2. Logout and try to login as an exisiting user, using the user name (not the email address) and a wrong password. The user account gets blocked after above set number of tries.
  3. After re-enabling the account, try to login using the email address (not the user name) and a wrong password. The user account does not get blocked after above set number of tries

Expected behaviour

The account should get blocked, no matter if the user name or its email address is used.

Actual behaviour

The account does not get blocked if the email address is used.

Server configuration

Nextcloud version: 21.0.5

Updated from an older Nextcloud/ownCloud or fresh install: updated

@LM-vb
Copy link
Author

LM-vb commented Oct 6, 2021

After upgrading to 22.2.0: this bug is still present.

@szaimen

This comment has been minimized.

@LM-vb
Copy link
Author

LM-vb commented Jan 24, 2023

On 25.0.3: this bug is still present and not fixed.

@joshtrichards joshtrichards transferred this issue from nextcloud/server Jan 1, 2024
@LM-vb
Copy link
Author

LM-vb commented Mar 7, 2024

NC 28.0.3: this bug is still present and not fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants