[Date Prev][Date Next] [Chronological] [Thread] [Top]

account schema problem

Hi all,
I am trying to see if I need to define a new set of attributes/objectclass if the only attributes required are
1. uid
2. userpassword
3. entitlement level
Can I just reuse the top and person objectclass to reuse the uid and userpassword attributes  but at the same time I don't want to specify all other attributes such as
cn, sn and givenname ? If so can someone give some guidances on how to come about doing this ?
What is the most efficient to design this kind of schema?
Also can someone enlight me on or give me some links to help me undering AUXILIARY and STRUCTURAL objectclass type and when do we use them ?