# New third party certificate

**URL:** <https://discuss.elastic.co/t/new-third-party-certificate/292988>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security, fleet\
**Created:** [December 27, 2021, 2:52pm UTC](https://discuss.elastic.co/t/new-third-party-certificate/292988 "2021-12-27T14:52:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![srkn66](https://avatars.discourse-cdn.com/v4/letter/s/bcef8e/32.png) [@srkn66](https://discuss.elastic.co/u/srkn66)\
**Post date:** [December 27, 2021, 2:52pm UTC](https://discuss.elastic.co/t/new-third-party-certificate/292988/1 "2021-12-27T14:52:42Z")

</div>

I have a question. Today I created and configured new ceritificates for fleet, kibana and my nodes with letsencrypt, (previously it was Elasticsearch-cerutil).  
When I add the certificates in .yaml I get an authentication error. Does this have something to do with Elasticsearch-setup-passwords?

---

<div class="post-metadata">

**Author:** ![derekmizak](https://avatars.discourse-cdn.com/v4/letter/d/b2d939/32.png) [@derekmizak](https://discuss.elastic.co/u/derekmizak)\
**Post date:** [December 29, 2021, 5:42pm UTC](https://discuss.elastic.co/t/new-third-party-certificate/292988/2 "2021-12-29T17:42:05Z")

</div>

What do you get in the log? However, you probably had passwords stored in keystore localy - passwords for private key.

---

<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:** [January 26, 2022, 5:42pm UTC](https://discuss.elastic.co/t/new-third-party-certificate/292988/3 "2022-01-26T17:42:42Z")

</div>

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