we have a java based application that connects to customer´s LDAP lookup server. Customer wants to get rid of any bind requests to version 2. So our R&D updated the option in the code as per documentation from Oracle (java.naming.ldap.version
The value of this property is a string that specifies the protocol version for the provider.) However when this is deployed in production...in tcpdump traces we see bind request for version 2 and version 3. (No failover due to issues observed)
I cant replicate this behaviour in test server (long story but its a legacy software has changed many hands over the years, so its possible that test and prod are entirely identical...also test will not have the same no of requests and hence issues as prod etc etc)
Anyone has come across this issue? Thanks for your time in advance.
13 2021-10-06 02:22:56.856380 172.29.129.150 217.171.130.8 LDAP 105 2 bindRequest(1) "cn=xxx" simple
14 2021-10-06 02:22:56.895004 217.171.130.8 172.29.129.150 TCP 68 16612 → 37036 [ACK] Seq=1 Ack=38 Win=14592 Len=0 TSval=117821307 TSecr=1359793477
15 2021-10-06 02:22:56.896298 217.171.130.8 172.29.129.150 LDAP 82 bindResponse(1) success