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

Incorrect password causes lockout #106

Open
dancunningham opened this issue Oct 29, 2015 · 0 comments · May be fixed by #275
Open

Incorrect password causes lockout #106

dancunningham opened this issue Oct 29, 2015 · 0 comments · May be fixed by #275
Assignees
Labels
2016 Needs re-triage; from 2016 or earlier bug A defect in design or behaviour

Comments

@dancunningham
Copy link
Member

OpenMRS locks out a user for 5 minutes after 7 incorrect login attempts in a row.

https://wiki.openmrs.org/display/docs/Administering+Users#AdministeringUsers-ManagingUserLockout

It looks like the client app keeps trying to log in even when it's getting back an "incorrect password" response.

This is on a per-user database so when all apps are sharing a user it's a lot more likely to happen.

Because the tablets keep trying periodically to log in they automatically hit the limit and get locked out.

Most appropriate fix is probably if the tablet sees it is getting an incorrect password response, it should stop trying until you edit the settings and hit "Apply" on either the server, username or password dialog.

To workaround this for now and unlock the user, in mysql I had to run:

delete from user_property where user_id=4 and property=‘lockoutTimestamp’;
delete from user_property where user_id=4 and property='loginAttempts’;
@dancunningham dancunningham added the bug A defect in design or behaviour label Oct 29, 2015
@llvasconcellos llvasconcellos self-assigned this Oct 30, 2015
llvasconcellos added a commit that referenced this issue Nov 18, 2015
@zestyping zestyping added the 2016 Needs re-triage; from 2016 or earlier label Jun 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2016 Needs re-triage; from 2016 or earlier bug A defect in design or behaviour
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants