Hello Onkar, I ran into a similar issue when connecting to a Red Hat LDAP server, using UID, and not a MS Exchange server, since that is what the sAMAccountName is used for. I used the following settings to make the ARDBC LDAP connection:
Host Name: ldap.host.com Port Number: 636 Bind User: uid=ldapuser,ou=service,dc=host,dc=com Bind Password: <password> Use Secure Socket Layer: Yes Certificate Database: <Path to java keystore; e.x. C:\LDAP\ldaptrust.jks> LDAP Date-Time Format: Generalized Time Failover Timeout: 3000 Directory Page Size: 1000 Base DN for Discovery: ou=people,dc=host,dc=com If you are not using SSL, this will make things much, much easier. Your default port for non-SSL is 389. If you are using SSL, ensure you have created your Java Keystore using the following command: Create the Cert Database: certutil -N -d <certDir> Import the certs into the keytool -import -noprompt -trustcacerts -keystore <PATH TO JavaKeyStore; i.e. C:\JKS\javakeystore.jks> -storepass <Password for JKS file> -alias <Provide an alias> -file <PATH TO Certificate file; i.e. C:\CERT\certificate.crt> There is a good bit of information on the Java Keystore in the AR System 8.1 documentation I hope this helps. Kevin Eldridge _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
