For many sites, running one or more {{slapd}}(8) that hold an
entire subtree of data is sufficient. But often it is desirable
-to have one {{slapd}}} refer to other directory services for a
+to have one {{slapd}} refer to other directory services for a
certain part of the tree (which may or may not be running {{slapd}}).
!if 0
as a special {{referral}} object at the delegate point.
The referral object acts as a delegation point, gluing two services
together.
-This mechanism allows for hierarchical directory services to to be
+This mechanism allows for hierarchical directory services to be
constructed.
-A referral object has an structural object class of
+A referral object has a structural object class of
{{EX:referral}} and has the same {{TERM[expand]DN}} as the
delegated subtree. Generally, the referral object will also
provide the auxiliary object class {{EX:extensibleObject}}.
If the server {{EX:a.example.net}} holds {{EX:dc=example,dc=net}}
and wished to delegate the subtree {{EX:ou=subtree,dc=example,dc=net}}
to another server {{EX:b.example.net}}, the following named referral
-object would be added to {{a.example.net}}:
+object would be added to {{EX:a.example.net}}:
-> dn: dc=subtree, dc=example, dc=net
+> dn: dc=subtree,dc=example,dc=net
> objectClass: referral
> objectClass: extensibleObject
> dc: subtree
-> ref: ldap://b.example.net/dc=subtree,dc=example,dc=net/
+> ref: ldap://b.example.net/dc=subtree,dc=example,dc=net
The server uses this information to generate referrals and
search continuations to subordinate servers.
to the entry {{EX:dc=subtree,dc=example,dc=net}} in server B indicating
that A holds the immediate superior naming context.
-> dn: dc=subtree, dc=example, dc=net
+> dn: dc=subtree,dc=example,dc=net
> changetype: modify
> add: ref
> ref: ldap://a.example.net/
{{EX:referral}} directive. The value is a list of {{TERM:URI}}s
referring to superior directory services. For servers without
immediate superiors, such as for {{EX:a.example.net}} in the example
-above, the server can be configured to use directory service with
+above, the server can be configured to use a directory service with
{{global knowledge}}, such as the {{OpenLDAP Root Service}}
-(http://www.openldap.org/faq/index.cgi?file=393).
+({{URL:http://www.openldap.org/faq/index.cgi?file=393}}).
> referral ldap://root.openldap.org/
However, as {{EX:a.example.net}} is the {{immediate superior}}
-to {{EX:b.example.net}}, {{a.example.net}} would be configured
+to {{EX:b.example.net}}, {{b.example.net}} would be configured
as follows:
> referral ldap://a.example.net/
-The server uses this information to generate referrals to
-operations acting upon operations not within or subordinate
+The server uses this information to generate referrals for
+operations acting upon entries not within or subordinate
to any of the naming contexts held by the server.
For those familiar with X.500, this use of the {{EX:ref}} attribute
H2: The ManageDsaIT Control
-Adding, modify, and deleting referral objects is generally done
+Adding, modifying, and deleting referral objects is generally done
using {{ldapmodify}}(1) or similar tools which support the
ManageDsaIT control. The ManageDsaIT control informs the server
that you intend to manage the referral object as a regular
projects / openldap / blobdiff