Ran in to an issue configuring HTTPS on Graylog 3.2 when it comes to the PKCS8 key. When starting the server, receive an error message in log for JerseyService: “Caused by: java.io.IOException: ObjectIdentifier() – data isn’t an object ID (tag = 48)” I’ve come across numerous other posts from ea…

Documentation shows that encrypted self signed keys should work but they don't. opened 01:21PM - 25 Feb 20 UTC (UTC) [VDAAustin] VDAAustin As shown in the following d…

First and final bump, to see if anyone has any thoughts or suggestions about this. This seems important and it’s concerning that this has been avoided for many months.

what steps did you have done to create the key? Is this a self signed certificate? How is that created?

I followed the provided documentation to create a self-signed certificate. I followed all commands and instructions. Others have done the same and have had the same issue: https://docs.graylog.org/en/3.2/pages/configuration/https.html I understand, from seeing many of your previous comments on o…

There are similar problems on all of this post. The only solution is to remove the password from the key. So that should be a fundamental problem. https://community.graylog.org/t/graylog-3-2-https-private-key-issue/15355/3 https://community.graylog.org/t/ssl-tls-for-input-problem/15177/5 https:/…

It makes no different if it’s self signed certificate or not. I don’t use a self signed certificate, and hat the same problem.

Thank you for this Information, I can go with this workaround until a fix will be there. :slight_smile:

Thank you @mpfz0r @x-wolverine-x @jan . I appreciate it!

Hello everybody, I have wasted a lot of time with this problem, and when I had finally discover how to proceed and go to open a post about this to comment my way to proceed I found this thread. The problem when used encrypted pkcs8 certs: Caused by: java.io.IOException: ObjectIdentifier () - dat…

Graylog 3.2 PKCS8 Encrypted Key Issue

Graylog Central (peer support)

mpfz0r (Marco Pfatschbacher) May 15, 2020, 8:15am 7

I can confirm this bug. Java 8 and 11 cannot handle most (or all?) encrypted pkcs8 keys.
I’m currently working on a fix.

Graylog 3.2 HTTPS private key issue

Topic		Replies	Views
Graylog 3.2 HTTPS private key issue Graylog Central (peer support)	3	2231	May 15, 2020
Enabling HTTPS for the Web GUI fails when using secured pk8 key file Graylog Central (peer support)	1	786	August 7, 2018
Getting JerseySevice Errors on my SSL Certificate's Private Key Graylog Central (peer support)	1	1972	November 5, 2018
Unsupported key type PKCS#1, please convert to PKCS#8 Graylog Central (peer support)	7	4302	March 23, 2017
Graylog HTTPS/TLS Key Store Error (FIXED) Graylog Central (peer support)	1	90	March 9, 2025

Graylog 3.2 PKCS8 Encrypted Key Issue

Related topics