upstream/openldap
1
0
Fork 0
mirror of https://git.openldap.org/openldap/openldap.git synced 2025-12-20 22:59:34 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

More clarifications

Browse source
This commit is contained in:
Kurt Zeilenga 2002-08-28 04:22:12 +00:00
parent 1e0cc6da35
commit 4114c96ccd
1 changed files with 21 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

34
doc/guide/admin/schema.sdf
View file

@ -417,31 +417,34 @@ any LDAPv3 server and easily construct directives for use with
{{slapd}}(8).
LDAPv3 servers publish schema elements in special {{subschema}}
entries (or subentries). {{slapd}}(8) publishes a single subschema
entry normally named {{EX:cn=Subschema}}. In a server which
supports a single subschema subentry, the DN of the subschema
subenty can usually be found by examining the value of the
{{EX:subschemaSubentry}} attribute type in the {{root DSE}}.
Other servers may publish multiple subschema entries. These
can be located by examining the {{EX:subschemaSubentry}} attribute
contained in the entry at the root of each administrative context.
entries (or subentries). While {{slapd}}(8) publishes a single
subschema subentry normally named {{EX:cn=Subschema}}, this behavior
cannot be expected from other servers. The subschema subentry
controlling a particular entry can be obtained by examining the
{{EX:subschemaSubentry}} attribute contained in the entry at the
root of each administrative context. For example,
> ldapsearch -LLL -x -b "dc=example,dc=com" -s base "(objectclass=*)" subschemaSubentry
To obtain the schema from a subschema subentry, you can use
ldapsearch(1) as follows (replace the search base as needed):
> ldapsearch -LLL -x -b "cn=Subschema" -s base "(objectclass=subschema)" attributeTypes objectClasses
where "cn=Subschema" is the value of subschemaSubentry returned in
the prior search.
This will return {{TERM:LDIF}} output containing many type/value
pairs. The following is an abbreviated example:
> dn: cn=Subschema
> objectClasses: ( 1.1.2.2.2 NAME 'myPerson' DESC 'my person' SUP inet
> OrgPerson MUST ( myUniqueName $ givenName ) MAY myPhoto )
> attributeTypes: ( 1.1.2.1.1 NAME 'myUniqueName' DESC 'unique name wi
> th my organization' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubst
> ringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 SINGLE-VALUE )
> attributeTypes: ( 1.1.2.1.2 NAME 'myPhoto' DESC 'a photo (applicatio
> n defined format)' SYNTAX 1.3.6.1.4.1.1466.115.121.1.40
> objectClasses: ( 1.1.2.2.2 NAME 'myPerson' DESC 'my person' SUP inet
> OrgPerson MUST ( myUniqueName $ givenName ) MAY myPhoto )
Capture the output of the search in a file and then edit the file:
@ -450,6 +453,7 @@ Capture the output of the search in a file and then edit the file:
^ replace attribute type with directive name
(e.g. {{EX:s/attributeTypes:/attributeType /}} and
{{EX:s/objectClasses:/objectClass /}}).
^ reorder lines so each element is defined before first use
^ continue long directives over multiple lines
For the three type/value pairs in our example, the edit should
@ -470,7 +474,7 @@ result in a file with contains of:
> MUST ( myUniqueName $ givenName )
> MAY myPhoto )
Save in an appropriately named file (e.g. {{F:my.schema}}).
Save in an appropriately named file (e.g. {{F:local.schema}}).
You may now include this file in your {{slapd.conf}}(5) file.
!endif
@ -478,10 +482,10 @@ You may now include this file in your {{slapd.conf}}(5) file.
H3: OID Macros
To ease the management and use of OIDs, {{slapd}}(8) supports
{{Object Identifier}} macros. The {{EX:objectIdentifier}} is used
to equate a macro (name) with a OID. The OID may possibly be derived
from a previously defined OID macro. The {{slapd.conf}}(5) syntax
is:
{{Object Identifier}} macros. The {{EX:objectIdentifier}} directive
is used to equate a macro (name) with a OID. The OID may possibly
be derived from a previously defined OID macro. The {{slapd.conf}}(5)
syntax is:
E: objectIdentifier <name> { <oid> | <name>[:<suffix>] }