# Why can't logstash accept any other ssl key format than PKCS8?

**URL:** <https://discuss.elastic.co/t/why-cant-logstash-accept-any-other-ssl-key-format-than-pkcs8/91961>\
**Category:** Logstash\
**Created:** [July 5, 2017, 4:53pm UTC](https://discuss.elastic.co/t/why-cant-logstash-accept-any-other-ssl-key-format-than-pkcs8/91961 "2017-07-05T16:53:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![raazeev64](https://avatars.discourse-cdn.com/v4/letter/r/7feea3/32.png) [@raazeev64](https://discuss.elastic.co/u/raazeev64)\
**Post date:** [July 5, 2017, 4:53pm UTC](https://discuss.elastic.co/t/why-cant-logstash-accept-any-other-ssl-key-format-than-pkcs8/91961/1 "2017-07-05T16:53:01Z")

</div>

I am trying to implement SSL security to the communication between FileBeat and Logstash. I have all the certificates and keys(server as well as CA) except for the format of the server key. I have that in PKCS12 and JKS format.

I tried creating the PKCS8 format from the PKCS12 format. But the authority of the certificate was unknown then. I had used the following set of Openssl commands -

```
openssl pkcs12 -in 'node-1-keystore.p12' -out certificatename.pem
openssl pkcs8 -in certificatename.pem -topk8 -nocrypt -out 'node-1.key.pk8'

```

Please help me out with this?

---

<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:** [August 2, 2017, 4:53pm UTC](https://discuss.elastic.co/t/why-cant-logstash-accept-any-other-ssl-key-format-than-pkcs8/91961/2 "2017-08-02T16:53:21Z")

</div>

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