Previous actions:
2. Specifying the LDAP binding method
In this section you can define the scope of you LDAP search and some additional options for your LDAP search. The following sections describe in detail the various possible configurations.
|
Time limit options (by default not set) |
Description |
|
Maximum search time |
Specifies the maximum time for the LDAP search. If the time limit is reached, the search is ended.
|
|
Page time limit |
Specifies the amount of time the UMRA client waits for a result set before terminating the search request. |
|
|
|
|
Size limit options (by default not set) |
|
|
Total size limit |
Specifies the size of the result set. If the result set reaches search he specified size, the result set is considered complete. |
|
Page size limit |
The maximum number of records to be processed by the domain controller and returned to the UMRA client before continuing the search. |
|
|
|
|
Cache results options (set by default) |
|
|
Cache result |
Specifies whether the result set should be cached to the client. For very large result sets, disabling caching will reduce memory consumption on the client. |
|
|
|
|
Scope options |
|
|
Search subtree, including all the children and the base object (default) |
The search includes the entire Active Directory structure below the search base |
|
Search one level of the immediate children, excluding the base object |
The search includes any immediate children (sub containers or OUs) |
|
Search base object only (result contains one object maximum) |
This means that only the search base object is included in the search and no child containers or OUs. The maximum number of objects returned is one.. |
|
|
|
|
Referral chasing options |
|
|
Never |
|
|
Subordinate referrals only |
This option needs to be selected if the LDAP search requires proceeding into parts of the directory tree that are not stored on the current domain controller. |
|
External referrals only |
The LDAP search needs to follow up references to an LDAP directory on another domain.
|
|
Always |
|
Referrals
Every domain controller holds information about the other domains in the forest in the domain controller's Configuration container. When an LDAP search in Active Directory requires action on objects that are located on another domain controller, the client is referred to a domain controller that holds the requested object. This way, clients can query the root domain and reach the appropriate domain controller without having to know the name or location of the child domain.
See also: