[Bug Report]: Incompatibility between Confluent.Kafka V2.2.15 and Confluent Platform V7.3

[solomonrodion]

Prerequisites

• I have searched issues to ensure it has not already been reported

Description

When attempting to create Consumer with CreateTopicIfNotExists method and connect to Confluent Platform V7.3 (which uses Apache Kafka 3.3), the latest version of Confluent.Kafka results in an error: "Disconnected while requesting ApiVersion: might be caused by incorrect security.protocol configuration (connecting to a SSL listener?) or broker version is < 0.10 (see api.version.request)".
It has been confirmed that security configuration is set properly.

Steps to reproduce

1. Install the latest version of Confluent.Kafka
2. Connect to Confluent Platform V7.3 using the latest version of Confluent.Kafka

services.AddKafka(kafka => kafka
.UseConsoleLog()
.AddCluster(cluster => cluster
.WithSecurityInformation(config =>
{
config.SaslPassword = "...";
config.SaslUsername = "...";
config.SaslMechanism = KafkaFlow.Configuration.SaslMechanism.Plain;
config.SecurityProtocol = KafkaFlow.Configuration.SecurityProtocol.SaslSsl;
})
.WithBrokers(new[] { "...:9092" })
.CreateTopicIfNotExists(topicName, 10, 1)

4. Observe the error "Disconnected while requesting ApiVersion: might be caused by incorrect security.protocol configuration (connecting to a SSL listener?) or broker version is < 0.10 (see api.version.request)"

Expected behavior

Successful connection to Confluent Platform V7.3 using the latest version of Confluent.Kafka

Actual behavior

Disconnected while requesting ApiVersion: might be caused by incorrect security.protocol configuration (connecting to a SSL listener?) or broker version is < 0.10 (see api.version.request)

KafkaFlow version

2.2.15

[ruiqbarbosa]

Hi @solomonrodion,

Thank you for your comment. It appears that the issue you're facing is related to the authentication options not being passed correctly.

This problem is likely linked to issue 380, which our team is currently addressing. Once we resolve that issue, it should also resolve the problem you mentioned.

[JoaoRodriguesGithub]

Hi @solomonrodion,

Thank you for your contribution.

We are sorry to provide feedback just now.

Can you please consider update to the latest KafkaFlow version and check if the issue still persist?

We see this action valuable to pursue this topic in the near future.