-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/kafka] SSL available when Kraft mode enabled? #43226
Comments
This issue might be caused by the way the JKS stores are created. The environment provides client and CA certificates along with their private keys and they are used to create the JKS stores.
|
Another thing I do not understand: when I do not provide the KAFKA_CERTIFICATE_PASSWORD in the environment variables or set a wrong value, the broker starts just fine, no exception. As the keystores are password-protected, I would expect an error at startup time. |
Have you tried passing -keyalg RSA to your keytool commands? Depending on the version of the JDK you got the keytool from, the cert may be getting generated with DSA. Since the version of kafka in the latest image is running with jdk 17, i believe an SSL connection with TLSv1.3 is preferred but DSA is no longer supported for that version of TLS. |
Hi @nvp152 |
Hi @zapho, I haven't been able to reproduce your issue using the following docker-compose:
In my case, I generated the certificates using the following script:
Here are my output logs:
|
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Thanks, @migruiz4. This was indeed a certificate generation issue. |
But I didn't have any problems using kafkajs and kafka-ui |
Hi @wedreamer, Could you please provide more details? I'm sorry but I do not understand your comment and how it is related to this topic. If you are experiencing any issues related to the |
Name and Version
bitnami/kafka:3.4
What architecture are you using?
amd64
What steps will reproduce the bug?
I'm trying to spin a Kafka broker in Kraft mode using TLS mutual auth for client connection. But it ends up with a SSL handshake failure when starting a client.
When starting this container, there is no error in the logs:
Looking into the container, the PKS files are there and can be accessed (root user):
but what looks suspicious is that the logs show no ssl configuration
There might be a configuration issue but there is no trace in the logs to understand where it could occur.
What is the expected behavior?
The kafka client can successfully connect via the TLS connection to the broker.
What do you see instead?
Running a Kafka client using the same keystore and trustore files used for the broker leads to a handshake issue:
Trying to check the TLS socker leads to the same kind of issue:
Matching log from the broker:
Additional information
Full broker logs
The text was updated successfully, but these errors were encountered: