I think you'll have to define an auxillary class and the add that to your OU classes. Then you have additional attributes from your auxillary class.

...

...

Shashi Ranjan Shashi.Ranjan@aricent.com schrieb am 24.11.2014 um 15:11 in

Nachricht c43a407986634f1e83460bf39a1f0b4a@GURMBXV03.AD.ARICENT.COM:

Hello,

I need to add two elements to organizationalUnit Object Class.

How can I do it without modifying the core.schema file? Is there a way to define two new attributes in my private schema file (local.schema) and then extend the object class organizationalUnit defined in core.schema? I do not want to modify the file core.schema.

I wish to deliver only my local schema file (local.schema) with other changes also.

P.S.: I m new OpenLDAP.

Thanks & Regards, Shashi Ranjan "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

Shashi Ranjan wrote:

I need to add two elements to organizationalUnit Object Class.

Which attributes?

How can I do it without modifying the core.schema file? Is there a way to define two new attributes in my private schema file (local.schema) and then extend the object class organizationalUnit defined in core.schema? I do not want to modify the file core.schema.

Basically you have three options:

1. Define a custom STRUCTURAL object class SUP organizationalUnit and create entries based on that.

2. Define a custom AUXILIARY object class and add that to already existing entries using organizationalUnit as structural object class.

3. Define a DIT content rule for organizationalUnit and use MUST/MAY/NOT to meet your requirements.

Usually I prefer to either do 1. or 2. depending on other needs. I use 3. with NOT quite often to forbid attributes really not used.

Ciao, Michael.