Table of contents
Collapse the table of content
Expand the table of content

Account Locking Policies

j-martens|Last Updated: 1/13/2017

To protect against brute force techniques that can be used to try and "guess" passwords on basic authentication and PAM authenticated user accounts, DeployR enforces automatic account locking when repeated authentication attempts fail within a given period of time for a given user account:

 * DeployR Authentication Failure Lockout Policy Configuration
 */ = true = 10 = 1800

By default, automatic account locking is enabled and activates following 10 failed attempts at authentication on a given user account. To disable this feature, set the following configuration property to false: = false

When enabled, a count of failed authentication attempts is maintained by DeployR for each user account. The count is compared to the value specified on the following configuration property: = 10

If the count exceeds the failures.limit value, then the user account is locked and any further attempts to authentication on that account will be rejected with an error indicating that the account has been temporarily locked.

To manage locked user accounts, the administrator has two choices. The chosen behavior is determined by the value assigned to the following configuration property: = 1800

If the lock.timeout value is set to 0, then locked user accounts must be manually unlocked by the administrator in the Users tab of the Administration Console.

If the lock.timeout value (measured in seconds), is set to any non-zero, positive value then a locked user account will be automatically unlocked by DeployR once the lock.timeout period of time has elapsed without further activity on the account.

By default, automatic account unlocking is enabled and occurs 30 minutes after the last failed attempt at authentication on an account.

© 2017 Microsoft