-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
-
False
-
Unset
-
CRCPLAN-132 - HCC | Managed Instance of Kafka
-
None
Currently, clowder-quarkus-config-source assumes that saslMechanism is SCRAM-SHA-512, which isn't true with managed kafka. I'm fairly certain will leave quarkus-based services unable to connect.
See https://github.com/RedHatInsights/clowder/blob/dc2ca16df0b081f0581ebf5b666a1ccd2acc54e9/tests/kuttl/test-kafka-managed/04-json-asserts.yaml having saslMechanism PLAIN, needing org.apache.kafka.common.security.plain.PlainLoginModule
Compare to saslMechanism SCRAM-SHA-512 (see https://github.com/RedHatInsights/clowder/blob/dc2ca16df0b081f0581ebf5b666a1ccd2acc54e9/tests/kuttl/test-kafka-strimzi-topic-auth/02-json-asserts.yaml ), which needs org.apache.kafka.common.security.scram.ScramLoginModule
Related:
RHCLOUD-19718RHCLOUD-19719- RHCLOUD-19725
RHCLOUD-19901
- relates to
-
RHCLOUD-19901 Update eventing-integrations to use Kafka authentication
-
- Closed
-
- mentioned on