Using pagination with pageSize=0 returns 0 records

[jonathanvila]

I'm using SearchWithPagination with a PageSize of 0 , as it is said in the documentation

A requested pagingSize of 0 is interpreted as no limit by LDAP servers.

But the result is always 0 rows.

If I set conn.Debug=true then I see
error running search query "(objectClass=person)": LDAP Result Code 203 "Debugging Error": ldap: cannot process packet to add descr

Specifying a value higher than 0 seems to work fine with no issues.

[cpuschma]

I managed to reproduce this and it seems that this is an implementation mistake from MS. I ran a paged search request with pageSize = 0 against both an Active Directory and a OpenLDAP server.

The OpenLDAP Server had the necessary page control and the cookie for the client to use for the next request (to request the next batch of entries).

The Active Directory server also responded with the paging control in it's response, but the cookie was empty. The LDAP client therefore aborted the paging request, as this matches the behaviour when all results have been fetched.

The cookie MUST be set to an empty value if there are no more entries to return (i.e., the page of search results returned was the last), or, if there are more entries to return, to an octet string of the server's choosing,used to resume the search.

I'll dig around a bit more later, but for now this looks like a implementation mistake from Microsoft.

[cpuschma]

I tried this with different Active Directory server on different domain levels. All answered in the same behaviour unfortunately, with no cookie in their SearchResponse. I suggest you use the maximum number of allowed results configured for your domain (which should be 10.000 by default)

[cpuschma]

See #499
Function has been marked as deprecated and will be removed/made private in future releases.