Bug 78417 - LDAP fields: CN vs. displayName
Summary: LDAP fields: CN vs. displayName
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: addressbook (show other bugs)
Version: 1.6.1
Platform: unspecified FreeBSD
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2004-03-25 00:09 UTC by mi+kde
Modified: 2015-04-12 10:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mi+kde 2004-03-25 00:09:47 UTC
Version:           1.6.1 (using KDE 3.2.1, compiled sources)
Compiler:          gcc version 3.3.3 [FreeBSD] 20031106
OS:          FreeBSD (i386) release 5.2-CURRENT

Our LDAP server is MS Exchange, as is the case in most installations out there, I believe.

After I figured out, how to make kaddressbook use it, address lookups works nicely, but the name is being selected from the standard ``cn'' field, instead of the non-standard ``displayName''. For example, my own entry has:

	cn=	TETM
	displayName=	TETERIN Mikhail
	mail=Mikhail.TETERIN@example.com

The address, that KMail will suggest will look like:

	TETM <Mikhail.TETERIN@example.com>

It would be nice if it were possible to configure, which fields KMail should use... With presets for the typical case of MS Exchange packaged in...
Comment 1 mi+kde 2004-07-07 19:11:25 UTC
Any news on this bug? Why can't addressbook check for presence of "displayName" field and use it instead of always using (the standard) "cn"?

This workaround for MS' poor design would make life much easier...
Comment 2 Jan de Visser 2004-07-07 19:31:19 UTC
In KDE3.3 you can map LDAP attributes to various kaddressbook fields. By default 'Common Name' maps to 'cn'. I guess you could map that to 'displayName'.

KControl->KDE Components -> KDE Resources Configuration -> Select your LDAP resource -> Edit -> 'Edit Attributes'

I have no idea if that actually works though. My LDAP server is OpenLDAP and works fine ;-)
Comment 3 mi+kde 2004-07-07 19:55:11 UTC
Can the LDAP-field mapping feature be backported to the 3.2.x branch?

I'll certainly use it, once 3.3 is _released_, but automaticly detecting and using displayName still seems like a good idea. No?

FYI, the Active Directory's LDAP-schema is documented here -- more improvements can, possibly, be made to kaddressbook with this information:

	http://www.unav.es/cti/ldap-smb/ldap-smb-AD-attributes.html

Yours,

	-mi
Comment 4 Jan de Visser 2004-07-07 20:14:37 UTC
(Mandatory disclaimer: I'm not a developer, I just lurk)

I don't think features are backported, just bugfixes, and this close to the 3.3 release (beta 1 was released today) I would think only security fixes apply.

As for the AD "detection": Some more digging revealed that in the attribute mapping dialog you can specify a template. 'Outlook' is a defined template, but AD is not. In the outlook template, common name is still mapped to 'cn', so I don't know what that is. I guess that an AD template could be added. 

(Hrrmm... some digging around tells me the whole template thing is not actually implemented very well yet. Very little data in them and hardcoded).
Comment 5 Andreas Gungl 2004-07-07 22:02:25 UTC
On Mittwoch, 7. Juli 2004 20:14, Jan de Visser wrote:
> I don't think features are backported, just bugfixes, and this close to
> the 3.3 release (beta 1 was released today) I would think only security
> fixes apply.
Well, in this case it is easy. KDEPIM 3.3 module will run on KDE 3.3 as well 
as on KDE 3.2.x. It's just a matter of waiting for packages or compiling 
from sources.

Comment 6 Jan de Visser 2004-07-07 22:21:48 UTC
The new LDAP kioslave stuff is in kdebase though...
Comment 7 mi+kde 2004-07-27 18:42:51 UTC
Mozilla has this same problem in automaticly substituting the e-mail addresses:

           http://bugzilla.mozilla.org/show_bug.cgi?id=241220

But its addressbook is smart enough to use displayName, when available.
Comment 8 Michael Leupold 2008-11-09 23:33:21 UTC
I guess this bug was forgotten. Should have been closed way back. Of course the fields are still configurable in trunk r881868 :)
Comment 9 Laurent Montel 2015-04-12 10:23:15 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.