Problem/Motivation

Currently, enabling the "notice_attempts_available" option, only applies for the final login set by "user_wrong_count".

Steps to reproduce

Proposed resolution

We should discuss on how to define this option when using "host_wrong_count" and "host_wrong_count_hard" and how this should be handled, when multiple login limits on both user and host are set.

Also we need to show the message for every incorrect login.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

JohnnyW created an issue. See original summary.

salvis’s picture

Have you set "Maximum number of login failures before blocking a user" to non-zero?

grevil’s picture

Version: 7.x-1.9 » 2.x-dev
Related issues: +#3328218: Adjust tests, so they don't fail anymore

This problem seems to be still relevant for the current 8.x release.

anybody’s picture

Category: Support request » Bug report
Priority: Normal » Minor

Thanks @Grevil, so let's make this a bug report.

Still this feature is not very important and you typically don't want to use this, to not inform the "potential bad guy" ;)
This is why I've marked this minor. Happy to see MR's here fixing this.

grevil’s picture

Title: Does not show login attempts notice » Make attempt notices available for "host_wrong_count" and "host_wrong_count_hard" instead of only showing for "user_wrong_count"
Issue summary: View changes

Update, this DOES kinda work, but only for the final login.

grevil’s picture

Title: Make attempt notices available for "host_wrong_count" and "host_wrong_count_hard" instead of only showing for "user_wrong_count" » Make attempt notices available for every wrong login attempt.
Issue summary: View changes
grevil’s picture

Furthermore, the message for the final login is broken:

You have used 2 out of 2 login attempts. After all 2 have been used, you will be unable to login.

We might actually remove this feature entirely... What do you think about this @Anybody?

anybody’s picture

Status: Active » Needs work

@Grevil no I don't think we should remove that. Might be helpful for SOME people. But the maintainers won't work on this issue as it's not very relevant. But happy to review MR's!

anybody’s picture

Category: Bug report » Feature request