Repository navigation
Conversation
…memberOf is not requested Pass the client's requested attributes from UserSearchInterceptor to LdapBackend.search() so LdapProxyBackend only resolves group memberships when memberOf (or *) is requested. Co-Authored-By: Claude Code <noreply@anthropic.com>
Contributor
Author
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
KNOX-3533 - Skip group membership resolution in LdapProxyBackend when memberOf is not requested
What changes were proposed in this pull request?
Pass the client's requested attributes from UserSearchInterceptor to LdapBackend.search() so LdapProxyBackend only resolves group memberships when memberOf (or *) is requested.
How was this patch tested?
Unit tests were updated for the new functionality.
Manual search queries were run against the LDAP proxy to compare the results and time. Proxy was configured with recursive member resolution and the default depth of 3
The LdapProxyBackend was exercised with with useMemberOf configured both on and off
results with useMemberOf on:
Since memberOf is enabled, this optimization saves time by skipping the recursive member resolution
results with useMemberOf off:
When useMemberOf is not enabled, group membership is found using searches per user. This leads to a large fan-out of searches if the number of users is large.
Integration Tests
Integration tests were run, but no new integration tests were added because there should be no change in the results retrieved through the LDAP Proxy.
UI changes
No UI changes