Closed Bug 12332 Opened 25 years ago Closed 21 years ago

[LDAP] Allow LDAP protocol version to be specified in prefs

Categories

(SeaMonkey :: MailNews: Address Book & Contacts, enhancement, P3)

enhancement

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 198168

People

(Reporter: phil, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: helpwanted)

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.
Target Milestone: M15
Status: NEW → ASSIGNED
Severity: normal → enhancement
QA Contact: lchiang → pmock
changing QA assigned to pmock@netscape.com
Phil found a way to weasel out of owning this bug.  Reassigning.
Assignee: phil → selmer
Status: ASSIGNED → NEW
Mass moving to M16 to get these off the M15 radar.  Please let me know if this
is really an M15 stopper.
Target Milestone: M15 → M16
[LDAP] in summary
Summary: RFE: Allow LDAP protocol version to be specified in prefs → [LDAP] Allow LDAP protocol version to be specified in prefs
LDAP to M30, nobody, helpwanted
Assignee: selmer → nobody
Keywords: helpwanted
Target Milestone: M16 → M30
Blocks: 36557
QA Contact: pmock → hong
is this bug still relevant with more recent software versions? (bug cleaning)

*** This bug has been marked as a duplicate of 198168 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.