Closed Janus88 closed 3 years ago
Hi @Janus88, I see in your configuration :
config.SecurityProtocol = SecurityProtocol.SaslSsl;
but I didn't see certificates configuration. Are you sure your configuration is right ?
and second, your exception throw from Confluent Kafka .Net client. Are you tried to consume messages from topic source with a basic consumer using Confluent Kafka Dotnet package ?
Yes I use the Confluent Kafka Dotnet Package as well in another project successful with the following configuration:
Like in the official sample from confluent:
I'm very sorry, I found my failure... I have two clusters, the username/password was for the other cluster. But instead of unauthorized this is the result...
Hum ok good ! Yeah I agree with you, error is not the expected error message what unauthorize happens.
The strang thing was that if I changed the password, I got an unauthorized. Perhaps the API Keys are managed for all clusters but have only access to the ressources of the assigned cluster. Indeed very strange, costed me many hours the last two days...
Description
I tried to run a simple sample application with a confluent cloud cluster (first kafka-streams-dotned try for me). When starting there appears a StreamsException: Unknown topic or partition.
As you can see the necessary topics do exist:
Perhaps there is a simple solution, but I don't have anymore ideas :-(