-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
fix paged search with multiple bases (LDAP) #13865
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
Conversation
Signed-off-by: Arthur Schiwon <[email protected]>
Signed-off-by: Arthur Schiwon <[email protected]>
MorrisJobke
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code makes sense 👍
|
/backport to stable15 |
|
/backport to stable14 |
parallel search is not compatible with paged search, but the letter is usually always applied. Signed-off-by: Arthur Schiwon <[email protected]>
8f0f9d8 to
c868892
Compare
juliusknorr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and works 👍
|
@juliushaertl is drone showing something different to me? Or, if that was from the second commit that introduced the integration test only, then this is what should have happened, otherwise the test wouldn't work. |
Yes, just checked the status on the 2nd commit, since the other one was not on the screen. 🙈 Sorry for the noise there. |
|
backport to stable15 in #13884 |
|
The backport to stable14 failed. Please do this backport manually. |
|

refactor (not to backport)will do as seperate PR, less messThere are a couple concepts in LDAP around the search. On is that parallel searches in multiple bases are allowed. The other one are paged searches, that allows to browse through the directory. Alas, they are incompatible to each other. Since we do paged results by default (if present, which in 99% is), we leave the parallel search asside. This PR goes the quick way with so it is easy to backport. A follow up PR will follow to refactor functions for 16.
Included is an integration test (commit 2) that establishes the failing scenario, commit 3 contains the simple, backportable fix.