[GH-ISSUE #698] Support the Paged Results Control (RFC2696) #247

New issue

Closed

opened 2026-02-27 08:16:08 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 08:16:08 +03:00

Owner

Originally created by @broeng on GitHub (Oct 5, 2023).
Original GitHub issue: https://github.com/lldap/lldap/issues/698

Originally assigned to: @broeng on GitHub.

I am dealing with some proprietary software that will happily connect and search lldap for users, as part of a user import, but fails the entire import because it assumes search results are always pageable, and is unable to locate the Paged Results Control in the response.

In my case, the software will happily accept any number of results, so a search response containing all results, and a Paged Results Control indicating no futher results available, would satisfy the implementation and allow the import to go through. I could imagine this to be a common usage pattern.

So, I'd like to propose we extend the search result response with a control list containing the Paged Results Control, with a zero length "cookie" indicating no further results.

Originally created by @broeng on GitHub (Oct 5, 2023). Original GitHub issue: https://github.com/lldap/lldap/issues/698 Originally assigned to: @broeng on GitHub. I am dealing with some proprietary software that will happily connect and search lldap for users, as part of a user import, but fails the entire import because it assumes search results are always pageable, and is unable to locate the Paged Results Control in the response. In my case, the software will happily accept any number of results, so a search response containing all results, and a Paged Results Control indicating no futher results available, would satisfy the implementation and allow the import to go through. I could imagine this to be a common usage pattern. So, I'd like to propose we extend the search result response with a control list containing the Paged Results Control, with a zero length "cookie" indicating no further results.