node-rdkafka 0.8.0 fails to connect because of SASL Handshake not supported by broker

[ibm-messaging]

node-rdkafka 0.8.0 fails to connect because of SASL Handshake not supported by broker

[mimaison]

@dennisseidel We've now updated the Nodejs sample to run the latest node-rdkafka (0.10).
Closing this, if you still have issues, feel free to re-open

[dennisseidel]

Ok the solution seems to be to change the parameter a bit to the following:

'metadata.broker.list': opts.brokers,
'security.protocol': 'SASL_SSL',
'ssl.ca.location': opts.calocation,
'sasl.mechanisms': 'PLAIN',
'sasl.username': opts.username,
'sasl.password': opts.password,
'api.version.request': true

then it works.

Update: Ok that was to fast from my side, it looked fine but now it throws the following:

{ severity: 3, fac: 'FAIL', message: '[thrd:sasl_ssl://kafka02-prod01.messagehub.services.us-south.bluemix.]: sasl_ssl://kafka02-prod01.messagehub.services.us-south.bluemix.net:9093/1: SASL mechanism handshake failed: Local: Timed out: broker\'s supported mechanisms: (n/a)' } Error from consumer:{"origin":"local","message":"authentication failure","code":-1,"errno":-1,"stack":"Error: Local: Authentication failure"}

[mimaison]

Yes we plan to update our sample app in the next few weeks.
Is there a particular feature you need from node-rdkafka 0.8 ? If not, we recommend you stick with 0.6.3 for now as it's the version we've tested the most.

[dennisseidel]

@mimaison Thanks for the answer. Not specifically I was just using node-rdkafka and did not take a look which version you used, so I was confused when it did not work :)

But it seems that:
'metadata.broker.list': opts.brokers,
'security.protocol': 'SASL_SSL',
'ssl.ca.location': opts.calocation,
'sasl.mechanisms': 'PLAIN',
'sasl.username': opts.username,
'sasl.password': opts.password,
'api.version.request': true

works. But also the structure of the message object has change. Anyway it works now for me so everything good. Thanks again for the response.