Invalid Username or Password when using Bind

    Applies to:
  • SecureAuth Identity Platform
  • Legacy SecureAuth IdP
Deployment model:
  • Cloud
  • Hybrid
  • On Premises
  • Version Affected:  All


    When using Bind as the Validate User Type, a subset of Users always receive "Invalid Password"



    Bind uses Distinguished Name. If there is a special character in the DN, it causes the Bind to fail, even when the Username is correct. 



    Check what is common for the Users that are failing. For example, if they are all in an OU that has a / in the name, it is likely that this is breaking the DN lookup. 

    If this can be corrected, please do. Alternatively, switching to Search is likely to fix the issue. 


    Special Considerations:

    A change in how we Bind should fix this issue in 19.07.01 HF 38, 20.06 HF 17, 21.04 HF12, 22.02 HF9 and 22.12 HF2 once they are released.


    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



    Please sign in to leave a comment.