SOLVED: problem with action-validate-ldap-connection step when running configwizard
kcibmer 1000007V7A Visits (4999)
We were having some significant problems trying to federate an LDAP repository with WebSphere Portal. The acti
It turns out that our password had an ampersand in it, which works great when connecting from an LDAP browser, or any other method. However, the script which the configwizard runs tries to execute the "ldapcheck" from a command session, and the ampersand trips it up. In the example above, the ldapPassword field was only four characters long (four stars), but our password was "Guns&Ammo". That was our clue that maybe the password was getting corrupted. Yup, everything after the ampersand got cut off and the ldapcheck would return a failure. We changed the password to something without an ampersand, and everything worked great.
Lesson learned: don't put an ampersand in your password if you want to run the configwizard.