Andres Tarallo <[EMAIL PROTECTED]> recently posted, in part:
We want to store in the tree contact information for all the people that
work and study at the university. People lie into three different
categories: staff, academic staff (teachers and researcher) and
students. Is not rare that a person belongs to two categories: a teacher
is part of the staff or a student is also a teacher or research
assistant.
That's the same as here at the University of New Hampshire,
so I'm willing to bet that it's a common situation for
universities in general. :-)
It seems to be more common to use 'low bushy' LDAP trees
rather than 'tall spiky' trees when you look at most real
world LDAP applications. In this case I would recommend
putting all of the people, employees and students, into a
single branch. You can use an attribute like
eduPersonAffiliation
which is defined in the eduPerson LDAP schema to sort out
the person's relation with the university. This is a
multi-valued attribute so a person could easily hold
multiple roles (staff *and* student, for example).
See:
http://www.educause.edu/eduperson
for more information about the eduPerson Object Class which
is designed specifically for the needs of higher ed
institutions.
The password question is trickier. We (unfortunately?) use
a single password for all of our applications via a single
sign-on system, so I can't offer you any real world advice
here. Perhaps someone else can make a recommendation?
...BC
--
+-------------------------[ [EMAIL PROTECTED] ]---+
| Bill Costa | No good
| 1 Leavitt Lane Voice: | deed...
| CIS/Telecom -- 2nd Floor +1-603-862-3056 |
| University of New Hampshire | Goes
| Durham, NH 03824 USA | unpunished.
+---------------[ http://pubpages.unh.edu/~wfc/ ]--+
---
You are currently subscribed to [email protected] as: [EMAIL PROTECTED]
To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the
SUBJECT of the message.
