You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Client failed to SSL handshake with brokers when SslCaPem is set to [intermediate CA] or [root CA] or [intermediate CA + root CA].
See [How to reproduce] for config used.
This behaves differently when using the "location" set of config (SslKeyLocation/SslCertificateLocation/SslCaLocation)
Difference in these aspects:
Not setting SslCaLocation, this works, I guess it looks up the root CA in my local cert store. Not working with the "pem" set of config.
Setting SslCaLocation to root CA pem file, this also works. Not working when setting SslCaPem to same cert.
Setting SslCaLocation to intermediate CA pem, this does not work unless EnableSslCertificateVerification is disabled. For "pem" set of config this does not work regardless of EnableSslCertificateVerification.
Setting SslCaLocation to pem that contains both intermedate and root CA, this works. Not working with SslCaPem.
I'm using 2.5.2 release, I believe there is something wrong with evaluation trust chain when using the Pem string settings.
Same pem string configs also works well with Java Kafka Client.
Another issue I noticed when testing things is that 2.5.2 client seems to fail the SSL handshake with kafka 2.50 brokers with working pem string configs for 1.8.2 client.
Description
Client failed to SSL handshake with brokers when SslCaPem is set to [intermediate CA] or [root CA] or [intermediate CA + root CA].
See [How to reproduce] for config used.
This behaves differently when using the "location" set of config (SslKeyLocation/SslCertificateLocation/SslCaLocation)
Difference in these aspects:
I'm using 2.5.2 release, I believe there is something wrong with evaluation trust chain when using the Pem string settings.
Same pem string configs also works well with Java Kafka Client.
Another issue I noticed when testing things is that 2.5.2 client seems to fail the SSL handshake with kafka 2.50 brokers with working pem string configs for 1.8.2 client.
How to reproduce
AdminClientConfig adminClientConfig = new AdminClientConfig
{
BootstrapServers = "xxxx",
SecurityProtocol = SecurityProtocol.Ssl,
SslKeyPem = "xxxx",
SslCertificatePem = "xxxx",
SslCaPem = "xxxxx",
SslKeyPassword = "xxxx",
}
Getting error:
0A000416:SSL routines::sslv3 alert certificate unknown: SSL alert number 46
CA certs used are Entrust L1K and root cert is Entrust G2.
OS: Windows 11.
Logs:
log.txt
Checklist
Please provide the following information:
The text was updated successfully, but these errors were encountered: