Revert "Add connection pooling settings to LDAP documentation" #1762
Conversation
This file contains 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
This reverts commit 23d38ab.
kolchfa-aws
approved these changes
Oct 28, 2022
|
Link to the issue being tracked in security repo: opensearch-project/security#2216 |
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.
Reverts #1698
After some investigation, we now realize there are two different backends for LDAP: LDAP and LDAP2. Recent and previous code additions for connection pooling settings keys were made against LDAP2, but OpenSearch guides users to configure the LDAP backend for implementations.
Therefore, we are reverting these changes to documentation until the problem between the two backends is resolved. At that point we will reintroduce this documentation.