# Adding AD users fails on password field

**URL:** <https://www.finalbuilder.com/forums/t/adding-ad-users-fails-on-password-field/5099>\
**Category:** Discussion\
**Created:** [November 4, 2013, 2:59am UTC](https://www.finalbuilder.com/forums/t/adding-ad-users-fails-on-password-field/5099 "2013-11-04T02:59:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![catenalogic](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/catenalogic/32/116_2.png) [@catenalogic](https://www.finalbuilder.com/forums/u/catenalogic)\
**Post date:** [November 4, 2013, 2:59am UTC](https://www.finalbuilder.com/forums/t/adding-ad-users-fails-on-password-field/5099/1 "2013-11-04T02:59:50Z")

</div>

When I select an AD user from the list, the screen says I have to enter a password, but the password field is not visible:

The password does not meet the requirements set in the password policy. These are:

- Password must be at least 6 characters.
- It must contain at least 1 lowercase letter.
- It must contain at least 1 uppercase letter.
- It must contain at least 1 digit.

I think that the password validation must be removed when using LDAP.

---

<div class="post-metadata">

**Author:** ![catenalogic](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/catenalogic/32/116_2.png) [@catenalogic](https://www.finalbuilder.com/forums/u/catenalogic)\
**Post date:** [November 4, 2013, 3:00am UTC](https://www.finalbuilder.com/forums/t/adding-ad-users-fails-on-password-field/5099/2 "2013-11-04T03:00:49Z")

</div>

Btw, I can bypass this by first adding a dummy password, then switch to the AD user.

---

<div class="post-metadata">

**Author:** ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)\
**Post date:** [November 5, 2013, 12:31pm UTC](https://www.finalbuilder.com/forums/t/adding-ad-users-fails-on-password-field/5099/3 "2013-11-05T12:31:03Z")

</div>

Thank you for reporting this. We have reproduced the bug and will have a new build out later today with a fix.
