Blank BindDN ldap field precludes conn. to server in moz. 1.5

RESOLVED EXPIRED

Status

MailNews Core
LDAP Integration
--
trivial
RESOLVED EXPIRED
15 years ago
10 years ago

People

(Reporter: gene smith, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux 2.2.16-22smp i686; en-US; m18) Gecko/20010110 Netscape6/6.5
Build Identifier:  Problem observed on win2k, moz 1.5 and linux rh6.1 moz1.5a - not on them now

I am entering this to describe a bug that seems to be fixed in 1.6 but I can't
find in mozilla. This is only to help someone who might see this problem in 1.5
or earlier version and to know to use 1.6 or later. 
Specifically, I have found that if the BindDN field is left blank in 1.5, no
attempt is made to connect to the specified ldap server. (If BindDN is non-blank
a password is requested which is appended to the BindDN field and sent after the
connect is made.) In 1.6, a blank BindDN does an anonymous (no p/w) bind and for
me works find.

Reproducible: Always

Steps to Reproduce:
1.Enter ldap name and server addr in moz 1.5.
2.Keep default port 389 (no ssl)
3.Enter a BaseDN 
4.Enter nothing in BindDN
5.Run tcpdump (or windump) and watch host myldapserver
6.Go to addr book and enter known user name on ldap server
Actual Results:  
On tcpdump no conn to myldapserver and no name(s) appears in ldap addr book.


Expected Results:  
Moz 1.5 should connect to myldapserver and network activity should occur
containing ldap data in clear text. However, this does work on 1.6.

Again, this works great in 1.6 but not in 1.5. Attempted to find this problem in
bugzilla to no avail. Sorry if a dup and already fixed but wanted to document my
problem for others who might run into this. Marking as trivial since it seems to
be fixed.
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.