-
-
Notifications
You must be signed in to change notification settings - Fork 188
Kafka Lag Exporter container fails with PKCS12 certificates when generated with JDK17 #270
Comments
Just tested with JDK11 generated keystores and fail on the same way:
|
Not sure if this 'll work in your case, but at work we had to add a Which is weird since that's also already in the Dockerfile generated. Maybe a new tag would already be enough to fix the issue? Although ideally swap Java 8 for 11, also given the support timeline for 8. |
Thanks for the workaround @timtebeek !
Agree. I was thinking the best solution could be around those lines. cc @seglo |
Yes, update to latest JDK will fix issue - root cause is https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8267599 |
I just released |
@seglo thanks for the heads up! Unfortunately, it's not fixing the issue:
(same as https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8267599)
|
Ok. I created a ticket for Java 11. Maybe that will help. #286 |
As of today this workaround no longer works, as CentOS Linux 8 is End Of Life. |
Haven't tested it, but seems like #297 already solves this? |
I'll be cutting a release shortly once I sort out the release process. Thanks for your patience. |
Kafka Lag Exporter v0.7.0 has been released. Please let me know how it goes! |
Is this still an issue, now that the container uses Java 17? I suggest closing it. |
Describe the bug
PKCS12 keystores are the default since Java 9[1].
Even though JDK 8 supports PKCS12, I found that when creating keystores with newer versions (e.g. 17) the container running JDK 8 is not able to read the keystore:
[1] https://openjdk.java.net/jeps/229
To Reproduce
Java versions tested:
Container Java version:
Laptop Java version:
Configuration:
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: