Troubleshooting
Problem
Security configuration task fails with "Could not connect to LDAP directory at specified host, port and SSL state"
Symptom
Running a ConfigEngine task for WebSphere Portal security (for example, validate-federated-ldap) results in:
action-validate-ldap-connection:
...
[ldapcheck] javax.naming.CommunicationException: ldaphost.yourcompany.com:389 [Root exception is java.net.UnknownHostException: ldaphost.yourcompany.com]
[ldapcheck] ERROR: 1
[ldapcheck] Could not connect to LDAP directory at specified host, port and SSL state. Target finished: action-validate-ldap-connection
Target finished: validate-federated-ldap
...
Resolving The Problem
Verify the LDAP host, port, and SSL state supplied to the configuration task in wkplc.properties. The specific properties will depend on which task you are running. Verify connectivity between the WebSphere Portal server and the LDAP server.
For the specific exception above, "java.net.UnknownHostException: ldaphost.yourcompany.com", ensure that the underlying operating system can resolve the hostname ldaphost.yourcompany.com. Use operating system tools such as ping, host, and nslookup. You may need to update either the hostname in wkplc.properties, the name server (DNS), or a local hosts file.
Was this topic helpful?
Document Information
Modified date:
03 December 2021
UID
swg21423691