How are LDAP fields mapped to Address Book fields?

[margol]

Does anyone know how Outlook 2003 maps LDAP fields to the addressbook? For
example, given the following LDIF:

dn: cn=Some Person,ou=contacts,dc=domain,dc=com
givenName: Some
sn: Person
cn: Some Person
o: Company
telephoneNumber: 123-456-7890
mail: (e-mail address removed)
objectClass: inetOrgPerson
objectClass: top

The CN, givenName, sn, mail and telephoneNumber show up. I'd expect o to
show up as "Company Name", but it doesn't. I want to add more fields, but am
taking them one at a time. Is there any up-to-date official reference of how
outlook 2003 maps LDAP fields to it's address book?

 

[Sue Mosher [MVP-Outlook]]

This looks like a pretty useful reference -- http://www.computerperformance.co.uk/Logon/LDAP_attributes_active_directory.htm

AD doesn't use o at all, at least not as one of its normal fields. For the company name, use company.

An alternative is to use ADSI edit. What I've done is edited a record to take each ADSI field and for its value use the field name. When I view that record in the Outlook address book, it's easy to match up the property name with the display name for the field.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[margol]

I'm actually using OpenLDAP, not AD.
However, I made some progress with your information.

I changed the schema for the o attribute to default to 'company' by changing
the following lines in the default core.schema file from:

attributetype ( 2.5.4.10 NAME ( 'o' 'organizationName' )
DESC 'RFC2256: organization this object belongs to'
SUP name )

to:

attributetype ( 2.5.4.10 NAME ( 'company' 'organizationName' 'o' )
DESC 'RFC2256: organization this object belongs to'
SUP name )

Now it works in Outlook 2003, but now no longer works in Oulook Express or
other clients who use the standard 'o' attribute...