Blizzard / Blizzard/node-rdkafka
Unable to connect MKS via ssl with node 18
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 403
- PR merge metrics
- No merged PRs in 30d
Description
**Environment Information**
- OS [e.g. Mac, Arch, Windows 10]: Alpine
- Node Version [e.g. 8.2.1]: 18.9
- node-rdkafka version [e.g. 2.3.3]: 2.16
Looks like there's a openssl comptability issue with librdkafka when using node 18.9. It works fine with node 12. Giving below error with node 18:
`{"message":"Failed to parse ssl.keystore.location PKCS#12 file: /usr/../kafka.client.keystore.jks: error:0308010C:digital envelope routines::unsupported: Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()","code":-172,"errno":-172,"origin":"kafka","stack":"Error: Failed to parse ssl.keystore.location PKCS#12 file: /usr/src../kafka.client.keystore.jks: error:0308010C:digital envelope routines::unsupported: Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()\n at Function.createLibrdkafkaError [as create] (/usr/src/app/node_modules/node-rdkafka/lib/error.js:456:10)\n at /usr/src/app/node_modules/node-rdkafka/lib/client.js:196:28"} `
Contributor guide
Research direction
Reproduce the failure in the Alpine, Node 18.9, and node-rdkafka 2.16 environment using the reported PKCS#12 keystore, then inspect node-rdkafka/lib/error.js and node-rdkafka/lib/client.js around the stack-trace locations. Compare the Node 12 and Node 18 behavior and verify that SSL keystore connections work without the reported RC2-40-CBC error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, kafka, node.js
- Domain
- backend, networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100