Feat/add elastic search api key authentication #379
Merged
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.
Add apiKey authentication method to elasticSearch target
Problem
Currently, the only available method to authenticate elasticSearch target is by using username/password in a Basic Http Auth Method.
This is a limitation and implies using login credentials from a user in the integration
Proposed Implementation
Adding the possibility to configure ApiKey authentication so the integration can be achieved by using an user personal apiKey instead of actual user credentials.