Forum Discussion
Client unable to bind to LDAPs through LTM virtual for LDAPS
This is my fully functional secureLDAP virtual configuration.
Steps I followed: 1) Requested certificate i.e. SecureLDAP.domain.com from our internal PKI team 2) Uploaded the cert ; thereafter created CLIENTSIDE ssl profile i.e. CLIENTSSL-secureldap 3) Identified Virtual Server IP i.e. 10.1.1.2; Created DNS record matching matching name in the cert 4) Started out by creating NODES of all AD servers 5) Created a Pool with NODES created in previous step 6) Created a virtual Server with IP : 10.1.1.2 Port 636 7) VS type - Standard ; Protocol : TCP ; Rest all default 8) Applied CLIENTSSL-secureLDAP under SSL PROFILE (Client) section 9) SSL PRofile (SERVER) : left empty 10) Source Address Translation : AutoMap 11) Under resources - assigned the POOL of AD servers created earlier.
Therafter downloaded, installed and launched Softerra LDAP Browser (FREE EDITION) Created a new profile with new LDAP name; defined the Bind username with password (IMP Step) First attempted to connection SSL connection check ; connection got refused Second time - attempted with SSL checkbox checked and connection got succeeded.
ltm virtual VS-int-secureLDAP { description "Internal SecureLDAP lookup against AD servers" destination 10.1.1.2:ldaps ip-protocol tcp mask 255.255.255.255 pool POOL-OF-MY-Active-Directory-Servers profiles { CLIENTSSL-secureldap { context clientside } tcp-lan-optimized { } } source 0.0.0.0/0 source-address-translation { type automap } vs-index 130 }
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com