Forum Discussion
Bug in F5 When configuring LDAPS (Secure LDAP). Please Fix F5 to accept hostname for Secure LDAP server pool connections.
Why it is an issue with F5's... Microsoft by default creates a cert that uses FQHN on domain controllers. By default in order to connect via LDAPS to Microsoft domain controller you must connect using FQHN, NOT IP. Big F5 only accepts IPs for LDAP which makes secure LDAPS fail to Microsoft Domain Controllers.
Work Around: Add an additional certificate on the Domain controller with IP as subject alternative name?
@ F5User-LB, please update the BUG ID for this and as per my understanding, let's say that the ssl certificate has been issued on the name of xyz.com, with it's IP being 1.2.3.4, you suggest that another certificate be issued for 1.2.3.4 as the name ?