Replies: 2 comments 5 replies
-
You should probably start by sharing the full log. |
Beta Was this translation helpful? Give feedback.
5 replies
-
Hi @iMaxZxC I believe this is a bug, I've opened #11228 and will work on a fix. The workaround you identified by creating a dummy Secret is valid. As far as I understand the User Operator cannot connect to a Kafka cluster that only has Sasl authentication. You can have three options:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm encountering an issue with the standalone User Operator (version 0.45.0) when attempting to manage users on a remote Kafka cluster (deployed on virtual machines, separate from my Kubernetes cluster). My setup does not use TLS, and I use SCRAM-SHA-512 for authentication with the credentials:
username: alice
password: alice-secret
I have set the following environment variables in my User Operator deployment:
Configuration Details:
My User Operator deployment (in namespace kafka) is configured as follows:
Since I'm not using TLS, I've created a dummy secret named unused in the kafka namespace:
JAAS Configuration: Is my JAAS configuration correct for SCRAM‑SHA‑512? (I'm using the single variable STRIMZI_SASL_JAAS_CONFIG with the value:
org.apache.kafka.common.security.scram.ScramLoginModule required username="alice" password="alice-secret";
Is that the recommended approach?)
TLS Requirement: Given that TLS is disabled (STRIMZI_TLS_ENABLED is "false"), is it expected that the User Operator still requires valid CA secrets? Is using a dummy secret like the one above a valid workaround?
Any Additional Configuration: Are there any other changes or workarounds required to run the User Operator successfully in a non-TLS environment with SCRAM‑SHA‑512?
Beta Was this translation helpful? Give feedback.
All reactions