-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
search returns max 500 users #46
Comments
Does your LDAP server acutally support paging? Try something like this to check:
If you don't get a result, the LDAP server doesn't support it. You can also request pagedResults explicitly and mark them es critical with the exclamation mark:
If the server doesn't support pagedResults, you'll get something like:
You can also use php to check, as shown here: https://www.php.net/manual/en/ldap.controls.php The code in LdapUtility.php:
doesn't seem to be a valid check for pagedResults support as the function even returned true in my tests, when pagination was marked as critical and the LDAP server didn't support pagedResults. To check for support it probably should be implemented like show'n in the php link I've pasted above. #18 points to the same issue if I'm not mistaken. |
This ticket is really old, there were many changes in master branch (upcoming v4.0.1) and possibly there is no more such bug... |
In LdapUtility.php:312
@ldap_control_paged_result( $this->connection, static::PAGE_SIZE, false, $this->paginationCookie );
returns true, but every time it runs into LdapUtility.php:377
// Should never happen unless pagination is not supported, for some odd reason if ($entries['count'] == static::MAX_ENTRIES) { break; }
So that means there is no paging, anyone any hint?
The text was updated successfully, but these errors were encountered: