...
| Note |
|---|
The new Syntaxes will use the OIDs 1.3.6.1.4.1.18060.1.1.0.1.N
The new MatchingRules will use the OIDs 1.3.6.1.4.1.18060.1.1.0.2.N
The new AttributesType will use the OIDs 1.3.6.1.4.1.18060.1.1.0.3.N
The new ObjectClasses will use the OIDs 1.3.6.1.4.1.18060.1.1.0.4.N Here, the prefix 1.3.6.1.4.1.18060 is the one declared to IANA to represent the Apache Foundation and the next 1.1 values are used specifically for Apache Directory. |
Syntaxes
We must define the minimum set of syntaxes.
...
Ordering is useless, so is Substr.
Description of CORE.SCHEMA
We now can define the schemas, using this meta schema
system
ObjectClasses
| Section |
|---|
| Column |
|---|
| | Code Block |
|---|
objectclass ( 2.5.6.0
NAME 'top'
DESC 'top of the superclass chain'
ABSTRACT
MUST objectClass
)
|
|
| Column |
|---|
| top is a very special ObjectClass, as it is the only one which can't be described with the MetaSchema, because top can't depend on itself because it can't exist before being created ! top will be hard wired in the server. Here is the LDIF file which could be used if we were to include it into the server :
dn: Name=top,cn=schema
objectclass=metaObjectClass
name: top
desc: top of the superclass chain
type: ABSTRACT
must: objectClass |
|
