I think that the FailedLoginAttempts system preference is only meant to be set ifNorwegianPatronDBEnable is set to 'Enable'; my testing is all done with ifNorwegianPatronDBEnable set to 'Disable'. What's happening: Setting FailedLoginAttempts, then logging in with incorrect credentials will lock the account. The login screen says that the account is locked, and no further attempts to log in will work. It is entirely unclear how to unlock the account -- resetting the password does not work, and the lock is not set via borrower debarments, so it can't be disabled there. The only way I was able to re-enable logins for a locked patron was to blank out FailedLoginAttempts. If this is only meant to be used in conjunction with ifNorwegianPatronDBEnable, it shouldn't be settable unless that is enabled.
Hi Barton, the preference is not related to ifNorwegianPatronDBEnable. See here: bug 18314 This login_attempts field is reset when a patron correctly logs in. When the account is locked the patron has to reset his/her password using the OpacResetPassword feature or ask a staff member to generate a new password.
Not a blocker - feature can be turned off (workaround) and no data loss: https://wiki.koha-community.org/wiki/Bug_Reporting_Guidelines#Severity
I have just quickly tested the feature on 17.05.x and everything works fine. Please read the description on the bug report and try again :) Changing the password unlock the account.
Looks invalid, please reopen if it is not.