OpenLDAP Extended User mode description for SLAPD

This chapter describes how to extend user mode for SLAPD. This chapter assumes that the reader is already familiar with the ldap/x.500 information model.

Part I: The published schema file details the optional schema definitions provided in the publication and where other definitions can be obtained. Part Two: The extended pattern details how to define a new schema item.

This chapter does not discuss how to extend the system pattern for SLAPD, which requires modifying the original code. The system pattern includes all the action attribute types, and any object classes that allow or require action attributes (direct or indirect).

Published schema files

OpenLDAP publishes a series of schema descriptions for your use. Each set is defined in a file that is suitable for inclusion (using the containing instruction) in your slapd.conf (5) file. These schema files are usually installed in the/usr/local/etc/openldap/schema directory.

Table 8.1:provided Schema http://www.aliyun.com/zixun/aggregation/29909.html ">specifications

FileDescription Core.schemaopenldap Core (required) Cosine.schemacosine and Internet X.500 (useful) Inetorgperson.schemainetorgperson (useful) misc.schemaassorted (experimental) nis.schemanetwork Information Services (FYI) Openldap.schemaopenldap Project (experimental)

To use these schema files, you only need to include the required files in the Global definition section of your slapd.conf (5) file. For example:

# include schema
Include/usr/local/etc/openldap/schema/core.schema
Include/usr/local/etc/openldap/schema/cosine.schema
Include/usr/local/etc/openldap/schema/inetorgperson.schema

Other files can also be obtained. Please refer to the OpenLDAP FAQ (http://www.openldap.org/faq/).

Note: You should not modify the definition of any schema item in the provided file.

Extended mode

Schemas for SLAPD (8) can be extended to support additional syntax, matching rules, attribute types, and object classes. This chapter details how to add user-applied attribute types and use syntax and matching rules that have been SLAPD supported. SLAPD can also be extended to support additional syntax, matching rules, and system patterns, but this requires partial programming and therefore is not discussed here.

There are five steps to defining a new pattern:

Obtain Object identifer
Choose a name prefix (select name prefix)
Create local schema file (creating native schema files)
Define custom attribute types (if necessary) (Define custom property type if needed)
Define custom object classes (define Custom objects Class)