KNOX-3422: Ldap Proxy used in-memory bind user - #1357
Merged
Conversation
The bind user created from the gateway configuration is now created in-memory instead of being added to the embedded ldap server. This provides the benefit of being able to rotate the user just by changing the configuration. Previously, since the configured user is not tracked, there wasn't a way to automatically rotate the user.
Contributor
Author
hanicz
requested changes
Aug 27, 2026
Test Results 3 files 3 suites 8s ⏱️ Results for commit 8f3c1a9. ♻️ This comment has been updated with latest results. |
hanicz
approved these changes
Aug 28, 2026
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
2 participants
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-3422 - Create LDAP Proxy bind user in-memory instead of in embedded LDAP
What changes were proposed in this pull request?
The bind user created from the gateway configuration is now created in-memory instead of being added to the embedded ldap server. This provides the benefit of being able to rotate the user just by changing the configuration. Previously, since the configured user is not tracked, there wasn't a way to automatically rotate the user.
How was this patch tested?
Unit test were updated and run.
Integration Tests
LDAP proxy search workflow tests were updated to use the configured bind user instead of a user in the remote LDAP.
A test was added to verify that anonymous bind does not work when the bind user is configured.
UI changes
no ui changes