302385 - LDAP attribute mapping for DisplayName still uses CN exclusively

Status: RESOLVED WORKSFORME

(MailNews Core :: LDAP Integration, defect)

Description

[John Peacock]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Using 1.1a2, it appears that the DisplayName field still uses CN, regardless of
the setting of 'ldap_2.servers.default.attrmap.DisplayName'.  This was supposed
to be fixed in 119291.

Reproducible: Always

Steps to Reproduce:
1. Create LDAP directory entry for server which provide 'displayname' differing
from 'CN'

2. Create Attribute map for ldap_2.servers.LanhamNW.attrmap.DisplayName to
include only 'displayname'

3. Look up any user in that LDAP database

Actual Results:  
DisplayName in AddressBook still shows the CN value and not the LDAP displayname
(tested with another LDAP browser)

Expected Results:  
DisplayName should be whatever the remote LDAP server returns as displayname

Tested vs Netware 6.5 eDirectory server as server and Softterra LDAP Browser 2.6

Comment 1

[zug_treno]

Duplicate of/related to bug 241220?

Comment 2

[John Peacock]

(In reply to comment #1)
> Duplicate of/related to bug 241220?

Not exactly.  The patch to fix bug 119291 was supposed to make *all* of the LDAP
attribute maps configurable and as a side effect made displayName preferred over
CN (as part of the default mapping).  Bug 241220, on the other hand, was all
about forcing the specific attribute displayName (and should probably be marked
as depending on bug 119291, which is the more general case).

The new bug 302385 is saying that post patch bug 119291, local prefs.js
attribute maps still don't work.  I just checked again and I cannot get either
DisplayName or Custom1 to work (under Thunderbird 1.1a2 with both Linux and
Win32).  It just so happens that the one I care about and reported is DisplayName.

Comment 3

[John Peacock]

OK, I finally figured out what is wrong here.  You can only set

user_pref("ldap_2.servers.default.attrmap.DisplayName","displayname");
                          ^^^^^^^

but you cannot set that on a server by server basis (which is what I was trying to do).  Once you add a default.attrmap, it does work correctly (i.e. the addressbook does show the DisplayName as published by the LDAP server).

I'm going to try and mark this as WORKSFORME, though it would be nice to be able to set this 

a) with the GUI;
b) on a server by server basis.

Thanks