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

[DOCS] Need elaboration in 'secure reporting endpoint' section to include both JKS or PEM options are supported #49969

Closed
elasticmachine opened this issue Aug 11, 2017 · 2 comments · Fixed by #54741
Assignees

Comments

@elasticmachine
Copy link
Contributor

Original comment by @hoigau:

In the latest documentation:

https://www.elastic.co/guide/en/kibana/5.5/securing-reporting.html

it's written like the truststore is the only option, but in fact it's also fine if the PEM equivalent settings are setup to trust the kibana server chain. It'd be good to have it elaborated that both the truststore or PEM option are supported, customer just need to setup one or another.

Configure Watcher to trust the Kibana server’s certificate by adding it to the Watcher truststore on each node:

Import the Kibana server certificate into the Watcher truststore using Java Keytool:

    keytool -importcert -keystore watcher-truststore.jks -file server.crt

   Note.  If the truststore doesn’t already exist, it is created.
    
Make sure the xpack.http.ssl.truststore.path setting in elasticsearch.yml specifies the location of the Watcher truststore. 
@jrodewig jrodewig transferred this issue from elastic/elasticsearch Nov 1, 2019
@elasticmachine
Copy link
Contributor Author

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

@jrodewig
Copy link
Contributor

jrodewig commented Nov 1, 2019

This touches Kibana docs. Transferring to the Kibana repo from the Elasticsearch repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants