Subject: LDAP paged result control
Author: krithiga
In response to: LDAP Search Paged Results Control
Posted on: 05/03/2012 03:10:00 AM
I have a requirement the i need to fetch all the records from AD even if it is more than 1000 entries. I tried using PagedResult control (from net) it works fine for filter which has less than 1000 entries. But if the filter fetches more than 1000 (that is needed)
(JAVA)
result is namingEnumeration
results.hasmore loop returns false and not going in to the loop.
What would be the reason it is failing?
Very urgent.Please help me in this regard.
Using the same code as above.
>
> On 09/06/2006 12:47:48 PM SteveHB wrote:
This control may be useful when the LDAP client has limited resources and may not be able to process the entire result set from a given LDAP query, or when the LDAP client is connected over a low-bandwidth connection.
The structure of this control is as follows:
pagedResultsControl ::= SEQUENCE {
controlType 1.2.840.113556.1.4.319,
criticality BOOLEAN DEFAULT FALSE,
controlValue searchControlValue
}
The searchControlValue is an OCTET STRING wrapping the BER-encoded version of the following SEQUENCE:
realSearchControlValue ::= SEQUENCE {
size INTEGER (0..maxInt),
-- requested page size from client
-- result set size estimate from server
cookie OCTET STRING
}
References:
