Opensearch access via LoginPassword or Certificate - #264
Open
bertrandrigaud wants to merge 13 commits into
Open
Conversation
bertrandrigaud
marked this pull request as ready for review
April 28, 2026 09:31
Contributor
|
The use cases you show make sense to me, however can you:
|
Contributor
|
Contributor
|
You need to at a minimum rebase this one, as there are conflicts. |
bertrandrigaud
force-pushed
the
oscertneo
branch
from
August 28, 2026 12:46
554cacb to
f5f082f
Compare
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.
Propose a way to manage both login/password and certificate for Opensearch DBs access :
The main idea is to have a default configuration used by DBs. Each DB is able to overide default values and to choose between login/pwd or certificate access (userCRT). By default useCRT is set to false.
Here are the different cases covered:
Related to #252