Lines Matching full:schema

5 H1: Schema Specification
7 This chapter describes how to extend the user schema used by
11 The first section, {{SECT:Distributed Schema Files}} details optional
12 schema definitions provided in the distribution and where to obtain
14 The second section, {{SECT:Extending Schema}}, details how to define
15 new schema items.
17 The third section, {{SECT:Transferring Schema}} details how you can
18 export schema definitions from an LDAPv3 server and transform it
22 This chapter does not discuss how to extend system schema used by
24 schema includes all operational attribute types or any object class
29 H2: Distributed Schema Files
31 OpenLDAP Software is distributed with a set of schema specifications for
34 file.  These schema files are normally installed in the
35 {{F:/usr/local/etc/openldap/schema}} directory.
38 	title="Table 8.1: Provided Schema Specifications"
40 core.schema		OpenLDAP {{core}} (required)
41 cosine.schema		Cosine and Internet X.500 (useful)
42 inetorgperson.schema	InetOrgPerson (useful)
43 misc.schema		Assorted (experimental)
44 nis.schema		Network Information Services (FYI)
45 openldap.schema		OpenLDAP Project (experimental)
48 To use any of these schema files, you only need to include the
52 >	# include schema
53 >	include /usr/local/etc/openldap/schema/core.schema
54 >	include /usr/local/etc/openldap/schema/cosine.schema
55 >	include /usr/local/etc/openldap/schema/inetorgperson.schema
60 Note: You should not modify any of the schema items defined
64 H2: Extending Schema
66 Schema used by {{slapd}}(8) may be extended to support additional
71 matching rules and system schema, but this requires some programming
74 There are five steps to defining new schema:
77 +	create local schema file
84 Each schema element is identified by a globally unique {{TERM[expand]OID}}
117 including identifying LDAP schema elements.
125 In addition to assigning a unique object identifier to each schema
131 names of other schema elements.  In particular, any name you choose
146 H3: Local schema file
149 directives can be used to define schema rules on entries in the
151 of your custom schema items.  We recommend you create a file
152 {{F:local.schema}} in {{F:/usr/local/etc/openldap/schema/local.schema}}
154 after other schema {{EX:include}} directives.
156 >	# include schema
157 >	include /usr/local/etc/openldap/schema/core.schema
158 >	include /usr/local/etc/openldap/schema/cosine.schema
159 >	include /usr/local/etc/openldap/schema/inetorgperson.schema
160 >	# include local schema
161 >	include /usr/local/etc/openldap/schema/local.schema
206 in {{F:core.schema}} as:
284 from {{F:inetorgperson.schema}} and replace the OID, name, and
396 H2: Transferring Schema
398 Since the {{slapd.conf}}(5) schema directives use {{REF:RFC4512}}
399 format values, you can extract schema elements published by any
403 LDAPv3 servers publish schema elements in special {{subschema}}
413 To obtain the schema from a subschema subentry, you can use
461 Save in an appropriately named file (e.g. {{F:local.schema}}).
477 and their use in defining schema elements: