Add the ability to use ApiKey based authentication #459
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
TrafeX
force-pushed
the
api-key-authorization
branch
2 times, most recently
from
8f95eb1 to
2267a5c
Compare
sysadmind
requested changes
Jul 26, 2021
Fixes prometheus-community#454 Signed-off-by: Tim de Pater <[email protected]>
Signed-off-by: Tim de Pater <[email protected]>
…nation Signed-off-by: Tim de Pater <[email protected]>
Signed-off-by: Tim de Pater <[email protected]>
TrafeX
force-pushed
the
api-key-authorization
branch
from
4107de9 to
41e0f4e
Compare
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.
If you're using Elasticsearch on Elastic Cloud the only way to authenticate is using API Keys.
This PR adds the ability to define the API Key and set it as Authorization header with every request.
Please let me know if I can improve anything about the implementation!
Fixes #454