badPwdCount is incremented by 2 each time a bad password is entered via an IdP realm

Follow

SecureAuth IdP Version Affected:  All

 

Description: 

When a user enters an incorrect password, 2 logon events are attempted to Active Directory, resulting in the AD attribute recording bad passwords (badPwdCount) to be incremented by 2 instead of the expectation that is should only increment by 1.

This can be observed using tools like ADSIEdit or the Microsoft Account Lockout Status tool (LockoutStatus.exe).

In domains where an account lockout policy is set this can lead to premature account lockouts. 

 

Cause

On the Data tab, the "Validate User Type" field is set to "Search".  When set this way it will make 2 logon attempts as the user each time the user tries to authenticate against the IdP realm.

  

Resolution

Set the "Validate User Type" field to "Bind" instead of "Search".  This will result in only a single logon attempt.

 

For more information on the differences between Bind and Search behaviour see this article:

https://support.secureauth.com/hc/en-us/articles/360020735892-LDAP-Provider-Bind-versus-Search

 

 

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.