Hello! I have a question regarding how the Entourage LDAP Directory
Services 'maps' to attributes in an LDAP server, in this case ADAM.

I have an ADAM directory with entries with the following attributes:

givenName, initials, name, mail, l, telephoneNumber, title, cn, and company,
displayName

I have my Directory Services in Entourage configured and working properly to
access this LDAP server. My question is, I want to include more data in
LDAP to be displayed when you open the 'ldap contact record'. What I do not
know, is the mapping of attributes in that contact record and attributes in
ADAM.

For example, l(locality) in ADAM is displayed in the 'City' field in the
'Work tab' for the contact. title in ADAM is displayed as 'Job Title'.
Company = Company, telephoneNumber = Work Phone, and mail = E-mail Address.

I also see Custom 1 - Custom 8 displayed on the various tabs as well.

So what I am looking for is a list of attributes found in a contact from the
Entourage Directory Services Tool, and how they would map over into the ADAM
LDAP directory.

Thanks for any help!

Gene

Re: LDAP Directory Services and Entourage by technology

technology
Sun Jul 03 19:09:46 CDT 2005

Gene,
I have Entourage Directory (and Apple Address Book) being populated via
our Apple LDAP server.
The mapping I've used are as follows:
LDAP Attribute Entourage 2004 Apple Address Book
sn Name Name
mail eMail Address Work email
o Company Company
ou Department
title Job Title Job Title
homePhone Home Home
telephoneNumber Work Work
mobile Mobile Mobile
jpegPhoto x Photo
?? Photo

Notes:
The jpegPhoto attribute is base64 encoded, I believe you can also use a
filepath to the jpeg images but I have not tested this.
objectClasses used: top, person, organization, inetOrgPerson

So the one oustanding issue I have is populating the photo in Entourage
- interested to know if anyone else has achieved this? I've had no joy
thru Microsoft support!

Cheers,
Gary


Re: LDAP Directory Services and Entourage by Nathan

Nathan
Wed Aug 10 18:13:17 CDT 2005

On 6/21/05 11:39:02 AM, in article uNhPACpdFHA.2688@TK2MSFTNGP14.phx.gbl,
"Gene Russell" <eugene.russell@msfc.nasa.gov> wrote:

> Hello! I have a question regarding how the Entourage LDAP Directory
> Services 'maps' to attributes in an LDAP server, in this case ADAM.
>
> I have an ADAM directory with entries with the following attributes:
>
> givenName, initials, name, mail, l, telephoneNumber, title, cn, and company,
> displayName
>
> I have my Directory Services in Entourage configured and working properly to
> access this LDAP server. My question is, I want to include more data in
> LDAP to be displayed when you open the 'ldap contact record'. What I do not
> know, is the mapping of attributes in that contact record and attributes in
> ADAM.
>
> For example, l(locality) in ADAM is displayed in the 'City' field in the
> 'Work tab' for the contact. title in ADAM is displayed as 'Job Title'.
> Company = Company, telephoneNumber = Work Phone, and mail = E-mail Address.
>
> I also see Custom 1 - Custom 8 displayed on the various tabs as well.
>
> So what I am looking for is a list of attributes found in a contact from the
> Entourage Directory Services Tool, and how they would map over into the ADAM
> LDAP directory.
>
> Thanks for any help!
>
> Gene

In 11.1.x and below (listed by Entourage field, in order of preference from
LDAP attributes):
Last Name: display_name, cn, commonname, sn, surname (the first three we
try to parse)
E-mail: mail, othermailbox, rfc822mailbox
First Name: givenname
Work state: st
Work country: c, co
Work company: o, organizationname, company
Work department: ou, organizationalunitname, department
Home web page: url
Home phone: homephone
Work fax: facsimiletelephonenumber, officefax
Personal cell: mobilephone
Pager: officepager, pager
Work title: title
Work phone: telephoneNumber
Work city: l
Home street: homepostaladdress
Work street: postalAddress, streetAddress, street
Notes: comment
Work zip: postalcode

In Entourage 2004, we also retrieve S/MIME certificates from
usersmimecertificate and usercertificate.

This is a static mapping, and not user editable. It may, however, change
from version to version.

The rest of the UI is the same as the regular contact UI but the fields
won't be filled in.

-nh

--
Nathan Herring
MacBU SDE/Development

This posting is provided ³AS IS² with no warranties, and confers no rights.


Re: LDAP Directory Services and Entourage by Nathan

Nathan
Wed Aug 10 18:52:23 CDT 2005

On 7/3/05 5:09:46 PM, in article
1120435786.383374.33560@g47g2000cwa.googlegroups.com,
"technology@learningmedia.co.nz" <technology@learningmedia.co.nz> wrote:

> Gene,
> I have Entourage Directory (and Apple Address Book) being populated via
> our Apple LDAP server.
> The mapping I've used are as follows:
> LDAP Attribute Entourage 2004 Apple Address Book
> sn Name Name
> mail eMail Address Work email
> o Company Company
> ou Department
> title Job Title Job Title
> homePhone Home Home
> telephoneNumber Work Work
> mobile Mobile Mobile
> jpegPhoto x Photo
> ?? Photo
>
> Notes:
> The jpegPhoto attribute is base64 encoded, I believe you can also use a
> filepath to the jpeg images but I have not tested this.
> objectClasses used: top, person, organization, inetOrgPerson
>
> So the one oustanding issue I have is populating the photo in Entourage
> - interested to know if anyone else has achieved this? I've had no joy
> thru Microsoft support!
>
> Cheers,
> Gary

This is not supported; we do not read jpegPhoto attribute values. I'll pass
it along to PGM as a feature request.

-nh

--
Nathan Herring
MacBU SDE/Development

This posting is provided ³AS IS² with no warranties, and confers no rights.


Re: LDAP Directory Services and Entourage by Chris

Chris
Thu Aug 11 01:53:15 CDT 2005

On 11/8/05 12:52, in article BF1FE147.77084%nathanh@online.microsoft.com,
"Nathan Herring [MSFT]" <nathanh@online.microsoft.com> wrote:

> On 7/3/05 5:09:46 PM, in article
> 1120435786.383374.33560@g47g2000cwa.googlegroups.com,
> "technology@learningmedia.co.nz" <technology@learningmedia.co.nz> wrote:
>> The jpegPhoto attribute is base64 encoded,

It should not be. The LDAP syntax used by the jpegPhoto attribute requires
the binary content of the JPEG file are used without any encoding.

It may get encoded using base64 when saving to LDIF, but that's a feature of
LDIF and not LDAP.

Cheers,

Chris