Howdy Folks!,

                                I am currently using openldap on a centos 5.x box which is working fine. However I was after some advice on configuring some of the overlays to get the results I am after.

 

The part I am looking at modifying is we currently have part of our ldap server ou=Contacts,dc=example,dc=com is reserved for our customer address book section.

We have choose to structure our Tree under in a hierarchy that represents belonging as follows

Our three object types are

A company is defined as objectClass ‘top’, ’organization’

A Person is defined as objectClass ‘top’, ‘organizaionalPerson’, ’inetOrgPerson’

A phone Number is defined as objectClass ‘top’, ‘room’

 

Under the root of the subtree can be either persons or companies

 

A company can contain persons or phone numbers

A person can contain phone numbers

 

The reason for arranging like this instead of assigning the phone number to the telephoneNumber field of a company or person is to allow multiple numbers to be entered against an object and name them (e.g. DDI, main, FAX, tech support, etc).

 

For most of our applications this is fine as we have written so they understand the hierarchy. My problem comes in specifically with VOIP phones that support a LDAP directory.

What I would like to do is manipulate the transparent overlay and rwm overlay take the following example

 

dn: cn=Joe Blogs,cn=contacts,dc=example,dc=com

objectClass: top

objectClass: organizationalPerson

cn: Joe Blogs

 

dn: cn=DDI,cn=Joe Blogs,cn=contacts,dc=example,dc=com

objectClass: top

objectClass: room

cn: DDI

telephoneNumber: 101

 

dn: cn=main,cn=Joe Blogs,cn=contacts,dc=example,dc=com

objectClass: top

objectClass: room

cn: main

telephoneNumber: 100

 

the phone does a ldap query (&(objectClass=telephoneNumber)(telephoneNumber=100))

that would return the last example object, but would display the name as ‘main’ what I was trying to do was overlay the parent object so it could use the cn from the parent object (or even better glue them together so we could get ‘Joe Bloggs, main’)

 

I understand the concept of the translucent overlay with something similar as follows that would overlay the destinations cn attribute locally as description. The tricky bit being configuring rwm to rewrite the dn for the lookup to grab it from the parent.

 

Overlay translucent

Uri ldap://localhost

Lastmod off

Map attribute description cn

 

 

 

Installed version: openldap-servers-2.3.43-12.el5_5.2