Introduction
We want to store the schema into ADS as any other entries. We have to define the minimum set of ObjectClasses an AttributeTypes needed to be able to bootstrap the schema.
All the ObjectClass will depend on the MetaObjectClass element, which is hard wired in the server.
All the AttributeTypes will depend on the MetaAttributeType element, which is hard wired in the server.
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
We will use OIDs 1.3.6.1.4.1.18060.1.1.0.0.N for Meta objects.
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.
Elements of the Meta-Schema
The MetaSchema will be presented in MetaSchema schema, but before, we must define some elements in this page.
Syntaxes
We must define the minimum set of syntaxes.
Those are following the following grammar (from RFC 4512 ) :
<SyntaxDescription> ::=
<LPAREN> <WSP>
<numericoid>
( <SP> "DESC" <SP> <qdstring> )?
<extensions> <WSP>
<RPAREN>
Only one is already defined: in http://www.rfc-archive.org/getrfc.php?rfc=4517
3.3.3. Boolean
A value of the Boolean syntax is one of the Boolean values, true or
false. The LDAP-specific encoding of a value of this syntax is
defined by the following ABNF:
Boolean = "TRUE" / "FALSE"
The LDAP definition for the Boolean syntax is:
( 1.3.6.1.4.1.1466.115.121.1.7 DESC 'Boolean' )
This syntax corresponds to the BOOLEAN ASN.1 type from [ASN.1].
They are the new one described in the following table :
Desc |
OID |
Extensions |
rules |
|---|---|---|---|
OID |
1.3.6.1.4.1.18060.1.1.0.1.1 |
- |
Must be a valid OID |
NameOrOid |
1.3.6.1.4.1.18060.1.1.0.1.2 |
- |
Must be a valid Name or a valid OID |
Type |
1.3.6.1.4.1.18060.1.1.0.1.3 |
- |
Should be one of those 3 strings :
|
Usage |
1.3.6.1.4.1.18060.1.1.0.1.4 |
- |
Should be one of those 4 strings :
|
MatchingRules
The Matching rules are deifned in RFC 4512 :
<MatchingRuleDescription> ::= <LPAREN> <WSP>
<numericoid> <MRParameters>
<SP> "SYNTAX" <SP> <numericoid>
<extensions> <WSP> <RPAREN>
<MRParameters> ::=
( <SP> "NAME" <SP> <qdstrings> |
<SP> "DESC" <SP> <qdstring> |
<SP> "OBSOLETE" )+
Here are the new MatchingRules :
Name |
OID |
Desc |
Obsolete |
Syntax |
Extensions |
|---|---|---|---|---|---|
OidMatch |
1.3.6.1.4.1.18060.1.1.0.2.1 |
Match an OID |
no |
OID |
- |
BooleanMatch |
1.3.6.1.4.1.18060.1.1.0.2.2 |
Match a Boolean |
no |
Boolean |
- |
NameOrOidMatch |
1.3.6.1.4.1.18060.1.1.0.2.3 |
Match a name or an OID |
no |
NameOrOid |
- |
TypeMatch |
1.3.6.1.4.1.18060.1.1.0.2.4 |
Match a type of ObjectClass |
no |
Type |
- |
UsageMatch |
1.3.6.1.4.1.18060.1.1.0.2.5 |
Match an attributeType Usage |
no |
Usage |
- |
ObjectClasses
The ObjectClass element is described in RFC 4512 :
<ObjectClassDescription> ::=
<LPAREN> <SP> <numericoid> <ocparameters> <extensions> <WSP> <RPAREN>
// Each parameters should not be seen more than once
<ocparameters> ::=
( <SP> "NAME" <SP> <qdescrs>
| <SP> "DESC" <SP> <qdstring>
| <SP> "OBSOLETE"
| <SP> "SUP" <SP> <oids>
| <SP> ( "ABSTRACT" | "STRUCTURAL" | "AUXILIARY" )
| <SP> "MUST" <SP> <oids>
| <SP> "MAY" <SP> <oids> )+
Here we have some elements which are already in the schema :
attributetype ( 2.5.4.0 NAME 'objectClass' DESC 'RFC2256: object classes of the entity' EQUALITY objectIdentifierMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 )
attributetype ( 2.5.4.13
NAME 'description'
DESC 'RFC2256: descriptive information'
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024}
)
attributetype ( 2.5.4.41
NAME 'name'
DESC 'RFC2256: common supertype of name attributes'
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768}
)
The other ones must be defined. Here is a table grouping all the missing elements :
Name |
OID |
Desc |
Sup |
Equality |
Ordering |
Substr |
Syntax |
SingleValue |
Collective |
NoUserModification |
Usage |
|---|---|---|---|---|---|---|---|---|---|---|---|
oid |
1.3.6.1.4.1.18060.1.1.0.3.1 |
The Object Identifier |
- |
OidMatch |
- |
- |
OID |
yes |
- |
yes |
dSAOperation |
obsolete |
1.3.6.1.4.1.18060.1.1.0.3.2 |
The type is obsolete |
- |
BooleanMatch |
- |
- |
Boolean |
yes |
- |
yes |
dSAOperation |
sup |
1.3.6.1.4.1.18060.1.1.0.3.3 |
The list of superiors |
- |
NameOrOidMatch |
- |
- |
NameOrOid |
no |
- |
yes |
dSAOperation |
must |
1.3.6.1.4.1.18060.1.1.0.3.4 |
The list of mandatory ATs |
- |
NameOrOidMatch |
- |
- |
NameOrOid |
no |
- |
yes |
dSAOperation |
may |
1.3.6.1.4.1.18060.1.1.0.3.5 |
The list of authorized ATs |
- |
NameOrOidMatch |
- |
- |
NameOrOid |
no |
- |
yes |
dSAOperation |
type |
1.3.6.1.4.1.18060.1.1.0.3.6 |
The ObjectClass type |
- |
TypeMatch |
- |
- |
Type |
yes |
- |
yes |
dSAOperation |
AttributeType
The AttributeType element is described in RFC 4512 :
<AttributeTypeDescription> = <LPAREN> <WSP> <numericoid> <atparameters> <extensions> <WSP> <RPAREN>
// Each parameters should not be seen more than once
<atparameters> ::=
(<SP> "NAME" <SP> <qdescrs>
| <SP> "DESC" <SP> qdstring
| <SP> "OBSOLETE"
| <SP> "SUP" <SP> <oid>
| <SP> "EQUALITY" <SP> <oid>
| <SP> "ORDERING" <SP> <oid>
| <SP> "SUBSTR" <SP> <oid>
| <SP> "SYNTAX" <SP> <noidlen>
| <SP> "SINGLE-VALUE"
| <SP> "COLLECTIVE"
| <SP> "NO-USER-MODIFICATION"
| <SP> "USAGE" <SP> <usage>)+
Here we have some elements which are already in the schema :
attributetype ( 2.5.4.13
NAME 'description'
DESC 'RFC2256: descriptive information'
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024}
)
attributetype ( 2.5.4.41
NAME 'name'
DESC 'RFC2256: common supertype of name attributes'
EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768}
)
The other ones must be defined. Here is a table grouping all the missing elements :
Name |
OID |
Desc |
Sup |
Equality |
Ordering |
Substr |
Syntax |
SingleValue |
Collective |
NoUserModification |
Usage |
|---|---|---|---|---|---|---|---|---|---|---|---|
obsolete |
1.3.6.1.4.1.18060.1.1.0.3.7 |
The type is obsolete |
- |
BooleanMatch |
- |
- |
Boolean |
yes |
- |
yes |
dSAOperation |
sup |
1.3.6.1.4.1.18060.1.1.0.3.8 |
The list of superior |
- |
nameOrOidMatch |
- |
- |
NameOrOid |
yes |
- |
yes |
dSAOperation |
equality |
1.3.6.1.4.1.18060.1.1.0.3.9 |
Equality matching rule |
- |
nameOrOidMatch |
- |
- |
NameOrOid |
yes |
- |
yes |
dSAOperation |
ordering |
1.3.6.1.4.1.18060.1.1.0.3.10 |
Ordering matching rule |
- |
nameOrOidMatch |
- |
- |
NameOrOid |
yes |
- |
yes |
dSAOperation |
substr |
1.3.6.1.4.1.18060.1.1.0.3.11 |
Substring matching rule |
- |
nameOrOidMatch |
- |
- |
NameOrOid |
yes |
- |
yes |
dSAOperation |
syntax |
1.3.6.1.4.1.18060.1.1.0.3.12 |
The attribute syntax |
- |
nameOrOidMatch |
- |
- |
NameOrOid |
yes |
- |
yes |
dSAOperation |
single-value |
1.3.6.1.4.1.18060.1.1.0.3.13 |
The attribute is single valued |
- |
BooleanMatch |
- |
- |
Boolean |
yes |
- |
yes |
dSAOperation |
collective |
1.3.6.1.4.1.18060.1.1.0.3.14 |
The attribute is collective |
- |
BooleanMatch |
- |
- |
Boolean |
yes |
- |
yes |
dSAOperation |
no-user-modification |
1.3.6.1.4.1.18060.1.1.0.3.15 |
The attribute is protected |
- |
BooleanMatch |
- |
- |
Boolean |
yes |
- |
yes |
dSAOperation |
usage |
1.3.6.1.4.1.18060.1.1.0.3.16 |
Type of operation |
- |
UsageMatch |
- |
- |
Usage |
yes |
- |
yes |
dSAOperation |
Ordering is useless, so is Substr.
Description of currently existing schemas
All the current schemas objects are described with the new syntax in those pages :
Schema |
ObjectClasses |
AttributeTypes |
|---|---|---|
apache |
||
apachedns |
||
autofs |
||
collective |
||
corba |
||
core |
||
cosine |
||
dhcp |
||
inetorgPerson |
||
java |
||
krb5kdc |
||
misc |
||
mozilla |
||
nis |
||
samba |
||
system |