Zhang Weiwu <[EMAIL PROTECTED]> kirjoitti:
Do you mean using a special attribute on business branch entry,
value of which is a DN referring to a person in ou=people?
No.
Or do you mean adding an attribute to each person entry which is a DN
referring to the business branch this person is working for?
Not exactly. I would do it more like this:
dc=foo,dc=com
. |
. +-ou=business units
. | |
. | +-ou=marketing
. | |
. | +-ou=sales
. |
. +-ou=people
. |
. +-john doe
. cn: john doe
. businessUnit: marketing
Then when you program a data-driven web application for your HR group to manage people,
you build a drop-down box of business units which are found in the above branch, so there
is no free text entry here. The objects in "ou=business units" could contain a
very small amount of metadata, such as description, and no child objects.
I hope this helps.
BR,
Mike
http://www.netauth.com - LDAP Directory Consulting
---
You are currently subscribed to ldap@umich.edu as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
