# Setting up Xpack security - stuck

**URL:** <https://discuss.elastic.co/t/setting-up-xpack-security-stuck/222766>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [March 9, 2020, 4:37pm UTC](https://discuss.elastic.co/t/setting-up-xpack-security-stuck/222766 "2020-03-09T16:37:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![amills](https://avatars.discourse-cdn.com/v4/letter/a/b782af/32.png) [@amills](https://discuss.elastic.co/u/amills)\
**Post date:** [March 9, 2020, 4:37pm UTC](https://discuss.elastic.co/t/setting-up-xpack-security-stuck/222766/1 "2020-03-09T16:37:50Z")

</div>

Hello everyone,

I recently setup a 3 server cluster of Elasticsearch, 2 server cluster of Logstash, and 1 Kibana server. Before I attempted to turn on https and xpack everything worked like a charm. I know I am getting confused around the certificates and CAs aspect.

I tried to make a CA on the master elasticsearch server and create keys to be used. For SSL I tried to create a wild card cert/chain to use on all of the servers using our domain CA.

We have our own CA and I am not really sure the best way to setup this all up. I would like to use our domain CA for as much as possible.

Below is what I have setup in the .yml file in elasticsearch:

#http.host: 0.0.0.0 # accept request from remote  
xpack.security.enabled: true  
xpack.security.transport.ssl.enabled: true  
xpack.security.transport.ssl.verification\_mode: certificate  
xpack.security.transport.ssl.key: certs/elasticsearch01.key  
xpack.security.transport.ssl.certificate: certs/elasticsearch01.crt  
xpack.security.transport.ssl.certificate\_authorities: ["/etc/elasticsearch/certs/ca.crt"]

xpack.security.http.ssl.enabled: true  
xpack.security.http.ssl.key: certs/http.key  
xpack.security.http.ssl.certificate: certs/http.crt  
xpack.security.http.ssl.certificate\_authorities: ["/etc/elasticsearch/certs/cachaincertificate.crt"]  
xpack.security.http.ssl.client\_authentication: optional

http.cors.enabled: true  
http.cors.allow-origin: "[https://website.com](https://website.com)"  
http.cors.allow-methods : OPTIONS, HEAD, GET, POST, PUT, DELETE  
http.cors.allow-headers : Authorization, X-Requested-With,X-Auth-Token,Content-Type, Content-Length

I have changed the name of some of the certs/website.

---

<div class="post-metadata">

**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\
**Post date:** [March 17, 2020, 10:55am UTC](https://discuss.elastic.co/t/setting-up-xpack-security-stuck/222766/2 "2020-03-17T10:55:29Z")

</div>

Hi ,

Is there a specific question we can help you with ? What is the problem / error you are getting with the configuration you tried ?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 14, 2020, 10:55am UTC](https://discuss.elastic.co/t/setting-up-xpack-security-stuck/222766/3 "2020-04-14T10:55:31Z")

</div>

Closed on April 14, 2020, 10:55am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.