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 lockout should be editable in dashboard #1358

Open
mtrezza opened this issue Oct 25, 2019 · 3 comments
Open

Account lockout should be editable in dashboard #1358

mtrezza opened this issue Oct 25, 2019 · 3 comments
Labels
bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature

Comments

@mtrezza
Copy link
Member

mtrezza commented Oct 25, 2019

Issue

When a user account is locked due to wrong password entered too many times, it cannot easily be unlocked. Customer support may want to unlock the account manually prior to the expiration date, for example upon customer request.

Unlock is currently only possible via edit directly in the database, which is not a practicable.

Suggested solution

The field _account_lockout_expires_at should be exposed in the dashboard to be manually deleted. Once the field value is deleted, the value for _failed_login_count becomes irrelevant and may as well continue to exist until it gets updated upon the next failed login attempt.

Alternative solutions

Add a design feature in the dashboard that indicates that a user is locked out and allow to unlock the user with the click of a button. -> more work to implement but provides the same functionality, so maybe a later PR.

Environment Setup

  • parse dashboard 2.0.4

Logs/Trace

@mtrezza mtrezza changed the title Account lockout should be visible in dashboard Account lockout should be editable in dashboard Oct 25, 2019
@davimacedo davimacedo added the type:feature New feature or improvement of existing feature label Oct 28, 2019
@stale
Copy link

stale bot commented Dec 12, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state:wont-fix Won’t be fixed with a clearly stated reason label Dec 12, 2019
@stale stale bot closed this as completed Dec 19, 2019
@mtrezza mtrezza added bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) and removed state:wont-fix Won’t be fixed with a clearly stated reason labels Oct 9, 2021
@mtrezza mtrezza reopened this Nov 2, 2021
@mtrezza mtrezza added bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) and removed bounty:$20 Bounty applies for fixing this issue (Parse Bounty Program) labels Nov 6, 2021
@mtrezza
Copy link
Member Author

mtrezza commented Oct 4, 2022

Since these are current internal Parse Server field (prefixed with _), there may be a change necessary in Parse Server as well. Exposing internal fields is always a sensitive topic, therefore before working on a PR we highly recommend a to discuss a suggestion for a solution.

@praharsha123

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty:$50 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

3 participants