Closed Bug 630816 Opened 11 years ago Closed 11 years ago

Newly created LDAP address books don't use to use the SSL port if specified


(MailNews Core :: LDAP Integration, defect)

Not set


(blocking-thunderbird5.0 needed)

Thunderbird 3.3a3
Tracking Status
blocking-thunderbird5.0 --- needed


(Reporter: standard8, Assigned: standard8)


(Keywords: regression)


(1 file)

This is a regression on trunk. If I create a new LDAP address book which is intended to connect to an SSL LDAP directory, then the server URI preference is of the form:

ldaps://<servername>/<rest of url>

If I do the same in 3.1 the the preference is of the form:

ldaps://<servername>:636/<rest of url>

Both should in theory work, as 636 is the default for LDAP SSL, however there's obviously an issue when not specifying the default port.
cc'ing Shaver and Justdave as I think this may have been one of the issues they were seeing with LDAP a week or so ago.
Attached patch The fixSplinter Review
Simple fix - if the URL is an SSL one, then use the LDAPS_PORT as default not the LDAP_PORT.
Attachment #509063 - Flags: review?(bienvenu)
blocking-thunderbird5.0: --- → needed
Comment on attachment 509063 [details] [diff] [review]
The fix

I tried clearing the port on an existing ldap address book using the properties dialog, and it silently set the port to 1, which is probably not what we want. But when I edited the uri by hand to remove the port, this code worked fine.
Attachment #509063 - Flags: review?(bienvenu) → review+
Checked in for today's nightly:
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 3.3a3
Application Build ID    20110204030014

You just made the cut before this build started ^^  :)

Verified.  My Mozilla address book works now. :)
(In reply to comment #5)
> Verified.  My Mozilla address book works now. :)

Excellent :-)
You need to log in before you can comment on or make changes to this bug.