Answers.Body: <p>It’s not currently possible to disable that behavior altogether, but you can increase the number of times the user can enter the incorrect password before their account gets locked using the <a href="http://buildwithcraft.com/docs/config-settings#maxInvalidLogins" rel="nofollow">maxInvalidLogins</a> config setting.</p>
  
  <p>You can also customize how long Craft will track invalid logins before that maxInvalidLogins counter resets using the <a href="http://buildwithcraft.com/docs/config-settings#invalidLoginWindowDuration" rel="nofollow">invalidLoginWindowDuration</a> config setting.</p>
  
  <p>For example you, if you wanted the users to get locked out if they entered more than two* incorrect passwords in 10 seconds, you could set these in craft/config/general.php:</p>
  
  <pre><code>'maxInvalidLogins' =&gt; 3, // see the note below
  'invalidLoginWindowDuration' =&gt; 'PT10S',
  </code></pre>
  
  <p>You can also customize what happens when a user gets locked out with the <a href="http://buildwithcraft.com/docs/config-settings#cooldownDuration" rel="nofollow">cooldownDuration</a> config setting. By default they will only be locked out for 5 minutes, so it’s not actually necessary for an admin to log in and unlock their account. That would only happen if the config setting was set to <code>0</code>.</p>
  
  <p><em>*There’s actually a bug in Craft right now where a user will get locked out as soon as they’ve hit the maxInvalidLogins count, which I think is incorrect; if the setting is set to 2, they should be able to login incorrectly 2 times, and still have a 6th chance to get it right. I’ve just adjusted that behavior for the upcoming 2.2 release.</em></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-08-23T14:58:34.350Z
Answers.LastActivityDate: 2014-08-23T14:58:34.350Z
Answers.UserDisplayName: Brandon Kelly
Body: <p>When a user forgets their password multiple times on one my front-end login screen, they sometimes get locked out of the system until an admin can unlock them in the control panel. Is there any way to prevent this behaviour?</p>
  
Tags: <users><password>
Title: How do you prevent user lockout?
ThreadText: # How do you prevent user lockout?
  
  (Asked by: username_0 on 2014-08-23)
  
  When a user forgets their password multiple times on one my front-end login screen, they sometimes get locked out of the system until an admin can unlock them in the control panel. Is there any way to prevent this behaviour?
  
  **Tags:** users, password
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-08-23. Score: 2 | Accepted answer
  
  It’s not currently possible to disable that behavior altogether, but you can increase the number of times the user can enter the incorrect password before their account gets locked using the [maxInvalidLogins](http://buildwithcraft.com/docs/config-settings#maxInvalidLogins) config setting.
  
  You can also customize how long Craft will track invalid logins before that maxInvalidLogins counter resets using the [invalidLoginWindowDuration](http://buildwithcraft.com/docs/config-settings#invalidLoginWindowDuration) config setting.
  
  For example you, if you wanted the users to get locked out if they entered more than two\* incorrect passwords in 10 seconds, you could set these in craft/config/general.php:
  
  ```
  'maxInvalidLogins' => 3, // see the note below
  'invalidLoginWindowDuration' => 'PT10S',
  
  ```
  
  You can also customize what happens when a user gets locked out with the [cooldownDuration](http://buildwithcraft.com/docs/config-settings#cooldownDuration) config setting. By default they will only be locked out for 5 minutes, so it’s not actually necessary for an admin to log in and unlock their account. That would only happen if the config setting was set to `0`.
  
  *\*There’s actually a bug in Craft right now where a user will get locked out as soon as they’ve hit the maxInvalidLogins count, which I think is incorrect; if the setting is set to 2, they should be able to login incorrectly 2 times, and still have a 6th chance to get it right. I’ve just adjusted that behavior for the upcoming 2.2 release.*
  
  
  ---
  
  