How to correctly configure Kafka source with SASL authentication in RisingWave?

I'm trying to set up a Kafka source in RisingWave with SASL authentication, but I'm encountering a GroupAuthorizationFailed exception. I've confirmed that the credentials are correct. Here's the configuration I'm using:

with (
   connector = 'kafka',
   topic = 'xxxxxxx', = 'xxxxxxxxxxxxx',
   properties.bootstrap.server = '',
   scan.startup.mode = 'latest', = 'true', = 'SASL_PLAINTEXT',
   properties.sasl.mechanism = 'SCRAM-SHA-256',
   properties.sasl.username = 'xxxxxxxxx',
   properties.sasl.password = 'xxxxxxxxxxxxxxx',
   properties.sasl.jaas.config = ' required username="xxxxxxx" password="xxxxxxxxxxxxx";', = '240000', = '240000'

Could the issue be related to the configuration format or is there something else I'm missing?


Michael Li

Asked on Jan 03, 2024

It seems like the configuration for SASL authentication might not be set correctly for Alibaba Kafka in RisingWave. Here's a configuration that was suggested to work:

create source s with (
  connector = 'kafka',
  topic = 'test',
  properties.bootstrap.server = 'endpoint', = 'SASL_SSL',
  properties.sasl.mechanism = 'PLAIN',
  properties.sasl.username = '<user>',
  properties.sasl.password = '<password>', = '/Users/wutao/only-4096-ca-cert'
) row format json;

Additionally, it was mentioned that the properties.sasl.jaas.config is not supported by RisingWave. If you are using a VPC endpoint to access Kafka, you should set the mechanism to 'PLAIN'. Also, ensure that your API key has access to the topic. If the issue persists, consider testing with a direct Rust implementation using rust-rdkafka to verify if the problem is specific to Alibaba Kafka or RisingWave.

Jan 04, 2024Edited by