Skip to content
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

Clarify the section on TLS for "Securing the reporting endpoints" #54741

Merged

Conversation

jportner
Copy link
Contributor

Closes #49969.

Since this section is focused on establishing trust for the Kibana server's certificate, I changed the documentation to describe the two most likely scenarios:

  1. The user has a CA certificate in a PKCS12 trust store, or
  2. The user has a CA certificate in PEM format

The old documentation recommended specifying the Kibana server's end-entity certificate as a trusted cert for Elasticsearch. I changed it to recommend specifying the CA certificate instead, which is what the rest of the Kibana documentation refers to regarding TLS connections and trust. This follows PKI best practices, as CA certificates usually have a much longer lifespan than end-entity certificates.

@jportner jportner requested a review from gchaps January 14, 2020 15:19
@jportner jportner added v7.6.0 v8.0.0 release_note:skip Skip the PR/issue when compiling release notes labels Jan 14, 2020
Copy link
Contributor

@gchaps gchaps left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-docs (Team:Docs)

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backported release_note:skip Skip the PR/issue when compiling release notes Team:Docs v7.6.0 v8.0.0
Projects
None yet
4 participants