# Missing Elastic Security and endpoint integration data

**URL:** <https://discuss.elastic.co/t/missing-elastic-security-and-endpoint-integration-data/246601>\
**Category:** Elastic Security\
**Tags:** elastic-agent\
**Created:** [August 27, 2020, 10:55am UTC](https://discuss.elastic.co/t/missing-elastic-security-and-endpoint-integration-data/246601 "2020-08-27T10:55:16Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![Nick\_Berlin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nick_berlin/32/74426_2.png) [@Nick\_Berlin](https://discuss.elastic.co/u/Nick_Berlin)\
**Post date:** [September 9, 2020, 4:16pm UTC](https://discuss.elastic.co/t/missing-elastic-security-and-endpoint-integration-data/246601/16 "2020-09-09T16:16:58Z")

</div>

FWIW, on an Ubuntu Linux VM, I was able to connect up an endpoint to elasticsearch using pki certificates. An issue I noticed was that I needed to restart endpoint in order for it to pick up changes in the system's trusted certificates.

I ran the following two commands in a root shell to add the certificate:

```
$ openssl pkcs12 -in certs/http.p12 -nokeys -out /usr/local/share/ca-certificates/elasticsearch-http.crt
$ update-ca-certificates

```

After restarting the endpoint, it was able to connect up fine.

Also, this particular line in elasticsearch's config

```
 xpack.security.http.ssl.truststore.path: certs/http.p12

```

did not affect the ability to connect, whether commented out or not.

---

_[View the full topic](https://discuss.elastic.co/t/missing-elastic-security-and-endpoint-integration-data/246601)._