283332 - LDAP query of Active Directory returns cn or commonname attr instead of displayname

Status: RESOLVED EXPIRED

(Thunderbird :: Address Book, defect)

Description

[Eric Hill]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When binding Thunderbird to Active Directory (W2003S), an LDAP query to the AD
server results in the email address being displayed as "netacct <email@domain>"
instead of "Network Account <email@domain>".  This is due (I believe) to the
order of the MozillaProperty_String descriptions for DisplayName, mapping cn and
commonname before displayname.  Active Directory uses the displayname attribute
as the primary name to display.  The common name in AD is the domain account
name, not the full user name.  Outlook and Outlook Express both show DisplayName
first.

Reproducible: Always

Steps to Reproduce:
1. Set up W2003S AD forest.
2. Add user to forest. (ehill, Eric Hill, eric@domain)
3. Config Thunderbird to LDAP query the forest.
4. Create a new message and type the users last name (Hill).

Actual Results:  
The email address displayed is "ehill <eric@domain>"

Expected Results:  
The email address should be "Eric Hill <eric@domain>"

Comment 1

[Eric Hill]

I confirmed this weekend that changing the account common name (cn) attribute in
Active directory to match the Display Name attribute side-steps the problem. 
It's not a proper fix, but it works.  It would be nice to be able to choose
which field coming back from LDAP is the primary name field before the email
address.

Comment 2

[Gervase Markham [:gerv]]

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/

Comment 3

[Gervase Markham [:gerv]]

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.