Sony Antony writes: > 1. Im deriving a custom user class from inetorgperson. > I need to make the mail attribute 'required' ( this is 'allowed' in > inetorgpersn )
Put mail in its list of MUST-attributes. A minimal object class definition would be ( <oid> NAME 'class name' SUP inetOrgPerson MUST ( mail ) ) > 2. Also when I have auxiliary objectclass s, and if teh same attribute > is defined as a different datatype, what will happen. Is this allowed > at all ? > ( Like mail is a DirectoryString in the structural base class whereas > it is a DN in the auxiliary/mix in class ) Not possible to even try to do. Attributes are defined independently of object classes. With regards to attributes, object class definitions just list which attributes MAY and MUST be present. You can define a different attribute named 'mail' and in another schema which controls another subtree, if your server supports that. However, you cannot mix the two schemas in the same subtree, so no subtree can use both definitions. > 3. If the same attribute is defined as 'allowed' in the structural > base class, but as required in teh auxiliary class, what will happen. Then the attribute is required. An attribute is required if it is required by any of the entry's object classes or their superclasses. -- Hallvard --- 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.
