Skip to main content

Improvements to Accounts Locked Due to Failed Login

Core Web App

This is really a 2 part request, but one is is required for the other.

1) Admins and Super Admins should be able to see if a user's account has been locked for failed logins.

2) At a minimum, Super Admins should have the ability to unlock accounts that are locked due to failed login rather than only being able to sit and tell the user to sit on their thumbs for the next 30 minutes.

The lack of ability to unlock either through the web interface or API results in a functional feature difference between self-hosted and magic cloud hosted customers, as self-hosted customers have the ability to reset by passing an exec to rails through docker.

4 comments

Log in to comment and vote

Comments4

  • Red Spool

    •

    Jun 9, 2023

    Yes, much needed. Espcially with the mobile app it is very ease to make mistakes when typing passwords. Being at a client's location with a locked account, and nothing to do but wait is very frustrating :D.

  • Plum Ash

    •

    Apr 30, 2023

    Had this happen to me last week, told support they should add some of the stuff you said and some info on their website about locked out users.

    Got this command that might release the user: «cd ~/hudu2 && sudo docker-compose exec app rails userreset:lock useremail=test@test.com» i didnt try it

    • Amber Fuelcell

      •

      May 1, 2023

      Emil A.: There is a documented unlock solution for self-hosted users. Magic Cloud users, however, are left with no choice but waiting.

    • Plum Burrito

      •

      Sep 3

      Kevin N. This should be upvoted as even today there is no solution.