-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libbeat/kibana: add ClientConfig.Headers #20580
Conversation
Add configurable headers to include in every request sent to Kibana. This is needed in some security applications, for authenticating the Beat.
Pinging @elastic/integrations (Team:Integrations) |
Pinging @elastic/integrations-services (Team:Services) |
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
... and Accept, and kbn-xsrf
Test failures are unrelated AFAICT. |
* 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)
* 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)
* 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)
* 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)
* 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
* 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)
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.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
nc -l 1234
setup.kibana.host: localhost:1234
, and a custom header insetup.kibana.headers
filebeat setup
Observe 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.