Schema definitions are created as entries in the
cn=schema,cn=config subtree. These entries must have the
olcSchemaConfig objectClass. As noted above, the actual
cn=schema,cn=config entry is predefined and any values specified
for it are ignored.
olcAttributetypes: ( <oid> [NAME <name>] [DESC <description>]
[OBSOLETE] [SUP <oid>] [EQUALITY <oid>] [ORDERING <oid>]
[SUBSTR <oid>] [SYNTAX <oidlen>] [SINGLE-VALUE]
[COLLECTIVE] [NO-USER-MODIFICATION]
[USAGE <attributeUsage>] )
Specify an attribute type using the LDAPv3 syntax defined
in RFC 4512. The slapd parser extends the RFC 4512
definition by allowing string forms as well as numeric
OIDs to be used for the attribute OID and attribute syntax
OID. (See the olcObjectIdentifier description.)
olcDitContentRules: ( <oid> [NAME <name>] [DESC <description>]
[OBSOLETE] [AUX <oids>] [MUST <oids>] [MAY <oids>]
[NOT <oids>] )
Specify an DIT Content Rule using the LDAPv3 syntax
defined in RFC 4512. The slapd parser extends the RFC
4512 definition by allowing string forms as well as
numeric OIDs to be used for the attribute OID and
attribute syntax OID. (See the olcObjectIdentifier
description.)
olcLdapSyntaxes ( <oid> [DESC <description>] [X-SUBST
<substitute-syntax>] )
Specify an LDAP syntax using the LDAPv3 syntax defined in
RFC 4512. The slapd parser extends the RFC 4512
definition by allowing string forms as well as numeric
OIDs to be used for the syntax OID. (See the
objectidentifier description.) The slapd parser also
honors the X-SUBST extension (an OpenLDAP-specific
extension), which allows one to use the olcLdapSyntaxes
attribute to define a non-implemented syntax along with
another syntax, the extension value substitute-syntax, as
its temporary replacement. The substitute-syntax must be
defined. This allows one to define attribute types that
make use of non-implemented syntaxes using the correct
syntax OID. Unless X-SUBST is used, this configuration
statement would result in an error, since no handlers
would be associated to the resulting syntax structure.
olcObjectClasses: ( <oid> [NAME <name>] [DESC <description>]
[OBSOLETE] [SUP <oids>] [{ ABSTRACT | STRUCTURAL |
AUXILIARY }] [MUST <oids>] [MAY <oids>] )
Specify an objectclass using the LDAPv3 syntax defined in
RFC 4512. The slapd parser extends the RFC 4512
definition by allowing string forms as well as numeric
OIDs to be used for the object class OID. (See the
olcObjectIdentifier description.) Object classes are
"STRUCTURAL" by default.
olcObjectIdentifier: <name> { <oid> | <name>[:<suffix>] }
Define a string name that equates to the given OID. The
string can be used in place of the numeric OID in
objectclass and attribute definitions. The name can also
be used with a suffix of the form ":xx" in which case the
value "oid.xx" will be used.
