On 17/04/2011 14:03, Stefan Seelmann wrote:

Hi George,

On Sun, Apr 17, 2011 at 12:07 PM, George Mamalakismamalos@eng.auth.gr wrote:

...

Dear all,

I have a question regarding my openldap DIT design. My design so far is based on the model: ou=people,dc=example,dc=com. It is very possible that I'll have to be able to find attributes of people belonging to some specific group (eg, student, postgrad, etc). The easiest way to address this issue for me would be to branch my DIT like this:

ou=undergrads,ou=people,dc=example,dc=com and ou=postgrads,ou=people,dc=example,dc=com. On the other hand, I have several classes that I would like to distinguish my users to apart from this (like stuff, student, professors, etc.) but further sub-brunching shows to me that there's something wrong with my design (since those classes may dynamically change in the future).

As a second solution I thought that it would be very easy to make my users in ou=people,dc=example,dc=com belong to some group located in ou=groups,dc=example,dc=com. This way I feel much more flexible in making such classifications, but my problem is how to formulate ldapsearch filters so as to return an attribute of some user only if the specific user belongs to one or more of my groups (for example to find all email accounts from my people that belong to the undergrads group).

A third approach is to to store the group as attribute in the user entries. The eduPerson schema [1] should fit your needs. Add the eduPerson object class to your user entries and use the eduPersonAffiliation multi-valued attribute to add the groups.

Kind Regards, Stefan

[1] http://middleware.internet2.edu/eduperson/

Stefan,

thank you very much for your advise. I had already included the eduperson schema in my configuration, but I had never seen this attribute in use. I will definitely take advantage of it, now that you told me its use.

Thanks again for your help,

regards,

George.