Cherry-pick #20580 to 7.9: libbeat/kibana: add ClientConfig.Headers #20699
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
* libbeat/kibana: add ClientConfig.Headers Add configurable headers to include in every request sent to Kibana. This is needed in some security applications, for authenticating the Beat. * Add setup.kibana.headers to config/docs * libbeat/kibana: prevent overridding Content-Type ... and Accept, and kbn-xsrf (cherry picked from commit 38fc1ed)
axw
added
[zube]: In Review
backport
Team:Integrations
botelastic
bot
added
the
needs_team
|
Pinging @elastic/integrations-services (Team:Services) |
botelastic
bot
removed
the
needs_team
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
urso
approved these changes
Aug 20, 2020
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
* libbeat/kibana: add ClientConfig.Headers Add configurable headers to include in every request sent to Kibana. This is needed in some security applications, for authenticating the Beat. * Add setup.kibana.headers to config/docs * libbeat/kibana: prevent overridding Content-Type ... and Accept, and kbn-xsrf (cherry picked from commit 88f95a7)
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.
Cherry-pick of PR #20580 to 7.9 branch. Original message:
What does this PR do?
Add configurable headers to include in every request sent to Kibana.
Why is it important?
This is needed in some security applications, for authenticating the Beat. Specifically, this is needed to fix elastic/apm-server#4065
Checklist
- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
nc -l 1234setup.kibana.host: localhost:1234, and a custom header insetup.kibana.headersfilebeat setupObserve the custom header is logged by netcat:
Related issues
elastic/apm-server#4065
Use cases
Introduces a means of specifying custom HTTP headers to add to all requests sent to Kibana. As above, needed in some security use cases.