Re: Schema extension - how to make attribute 'company' mandatory

[Edward van der Maas]

bwisupport wrote:

>
> Hello forum,
>
> because the native eDir 'user' class does'nt really fit our needs, I
> created an new user class called 'BWI:DDMuser' and populated it with
> some if our own attributes. Superclass of 'BWI:DDMuser' is the native
> 'user', so all attributes
> where inherited. Then I flagged the inherited optional attribute
> 'company' as
> 'use for naming' and expected the attribute to become mandatory.
> But this was'nt successfull. Our own mandatory attributes are
> mandatory,
> the inherited 'company' was'nt.

Having a naming attribute doesn't mean it is a mandatory attribute.

I reckon you'll have to create a new Class with ndsLoginProperties as a
superclass and then add all the additional attributes you want. I
wasn't able to create a class with User as a super class and flag
company as a mandatory attribute

--
Cheers,
Edward

[Lothar Haeger]

-------------- bwisupport wrote:

> An exception to the rule is when an optional attribute is used for
> naming, the attribute then becomes mandatory."

this is only true if if that op attr is the only naming attribute, I guess. If you've got multiple naming attributes you do not have to fill them all usually. Look at the standard user class: CN, uniqueID and OU are naming attributes, CN and Surname are mandatory. Seems like only one naming attribute has to mandatory, additional ones can as well remain optional.

Cheers, Lothar

PS: wherever you found that doc, fill in the comment fields at the bottom of the page and ask Novell to correct this, please.

--