Blizzard / Blizzard/node-rdkafka
How to use truststore.jks & keystore.jks files to build a producer application in .NET using Confluent Kafka
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 403
- PR merge metrics
- No merged PRs in 30d
Description
I have received truststore.jks & keystore.jks file from a team who manages kafka. We are required to build a producer application in .NET using these .jks files. I have used below commands to convert .jks files to required format as .jks is not compatible with .net applications.
keytool -importkeystore -srckeystore truststore.jks -destkeystore truststore.p12 -deststoretype PKCS12
openssl pkcs12 -in truststore.p12 -nokeys -out truststore.cer.pem
keytool -importkeystore -srckeystore keystore.jks -destkeystore keystore.p12 -srcstoretype jks -deststoretype pkcs12
openssl pkcs12 -in keystore.p12 -out keystore.pem
openssl rsa -in keystore.pem -out newrsakeystore.pem
Output of above commands are assinged to producer config properties as below:

After running getting error: "SSL Handshake failed. client SSL Authentication might be required (see ssl.key.location and ssl.certificate.location)"

Could anyone please help what wrong i am doing here?
_Originally posted by @dsanan0714 in https://github.com/Blizzard/node-rdkafka/issues/563#issuecomment-1122266781_
Contributor guide
Research direction
Review the producer configuration shown in the issue, focusing on ssl.key.location and ssl.certificate.location. Compare the converted PEM files and their certificate or key contents with the required client-authentication settings; done means the producer completes its SSL handshake.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, distributed-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100