ApiKey authentication - #801
Open
Albert (alozano3) wants to merge 8 commits into
Open
Conversation
|
🎉 All Contributor License Agreements have been signed. Ready to merge. |
|
|
Albert (alozano3)
force-pushed
the
feature-auth-apikey
branch
from
October 11, 2024 15:37
52a4b37 to
25095bf
Compare
|
Hi all, anyone looking into this ? Do you need help ? |
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.
Problem
There is no support for ApiKey Header authentication which is used in ES cloud version
Solution
Add a new property to put the API Key and use it to authenticate. It also checks if basic authentication is configured.
Does this solution apply anywhere else?
If yes, where?
Test Strategy
Testing done:
Release Plan