We have moved to GitHub Issues
Created by Shannon Deminick 14 Sep 2015, 12:44:41 Updated by Sebastiaan Janssen 16 Mar 2017, 08:37:43
This is because on a new installation the password format is plain text and when we try to change it, it goes through the full validation process. When this setting is false, the password cannot be updated and the installation fails.
Changing this to true after installation is ok though.
User should be able to enalbe account if his account has been disabled /umbraco access by someone attacked. You can give a enable link and send it to user email. It's very easy to do it.
Or another way let user account no need to disabled /umbraco access, Just simple let user must wait 3-5 seconds to try next login operation. if someone make mistakes 5 times, you can let him wait 1-30 minutes to try again.
Fixed in rev: 172ef8c379894023f25cceacc7db6839906c164c
Perfect! Thanks @Shandem !
Backwards Compatible: True
Due in version: 7.6.0
Sprint: Sprint 54