Article:
 |
|
Demystifying LDAP Data
|
| Subject: |
|
Inheritance Order on ldif |
| Date: |
|
2007-02-01 08:18:32 |
| From: |
|
fredcwbr
|
|
|
I'm getting through a lot of trouble in understanding the whole AUXILIARY/STRUCTURAL inheritance definition on a ldif, and the syntax that is needed for the correct definition.
Ex.
snip ---->>
objectclass ( 1.3.6.1.4.1.15490.2.1 NAME 'objCollege'
SUP top STRUCTURAL
DESC 'object class'
MUST (collegeName $ collegePrincipal $ collegePresident $ collegeSecretary )
MAY (collegeBoardMember ) )
dn: o=college
o: college
objectclass: organization
objectclass: objCollege
objectclass: top
Description: top object class
collegeName: ABC Engineering college
... and the rest follows?
---->><<<
wouldn't it be the same as
dn: o=college
objectclass: top
objectclass: organization
objectclass: objCollege
o: college
Description: top object class
... >> and the rest follows .???
|
Showing messages 1 through 4 of 4.
-
Inheritance Order on ldif
2007-02-01 08:32:48
Brian K. Jones | 
[View]
-
Inheritance Order on ldif
2007-02-01 11:46:47
fredcwbr
[View]
-
Inheritance Order on ldif
2007-02-01 11:57:28
Brian K. Jones | 
[View]
-
Inheritance Order on ldif
2007-02-01 12:24:22
fredcwbr
[View]
"I've done it starting with top and listing the descendants in order, like a family tree. You're free to list them out of order if you like."
That is not to say that I condone listing things out of order - I don't. However, I'm unsure that there is a product that will enforce this ordering of objectclasses in a given entry.
If the product you're using does not enforce the ordering, then the answer to your question "aren't these the same?" is "yes". If your product *does* care about the ordering, then the answer is "no", and you'll have to reorde the objectclass attributes of the entry.
If you're unsure how to do that, re-read this article, and you should be able to figure it out. If not, list your questions here! :-)