In Communicator 4.x, we apparently always bind to the directory server using LDAPv2. We should probably bind using LDAPv3, especially since we use some v3 features. Seems like we should add some preferences like this: ldap_2.hostname.protocolVersion, 3 ldap_2.hostname.protocolVersionFallback, true Where the protocolVersion pref gives the number we bind as, e.g. LDAPv2, LDAPv3, etc. The protocolVersionFallback would control what we do when binding using protocolVersion fails: true for fall back to the previous rev, or false for the connection to fail out with an error message. The technote: http://warp/server/directory-server/clientsdk/hammerhead/technotes/version-detec t.html explains how to bind to the LDAP server using a particular protocol version.
changing QA assigned to email@example.com
Phil found a way to weasel out of owning this bug. Reassigning.
Mass moving to M16 to get these off the M15 radar. Please let me know if this is really an M15 stopper.
[LDAP] in summary
LDAP to M30, nobody, helpwanted
is this bug still relevant with more recent software versions? (bug cleaning)
*** This bug has been marked as a duplicate of 198168 ***