-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SASL_SSL setup - Failed to create consumer for offset topic for cluster #425
Comments
I have configured it to use the sasl.mechanism to be 'PLAIN' as well , it seems to be using 'GSSAPI'. Were you able to figure out what is overriding here? Edit: Seems like it doesnt have the option to provide the sasl.mechanism to be used, it defaults to GSSAPI. |
@priashah No, I haven't looked at it since I logged that issue :( Although in the code it seems that it takes |
Please see my comment on #495; found that issue before this one. |
Thanks @lllewellyn , I did make the enhancement to read the values from the cluster page. It works that way. |
Hi all, I'm facing the exact same issue... and cannot make it working. Is there a workaround ? Best, |
Hi Jerome, |
Hi @priashah , Yes I saw it but did not try as I would refer to have it properly integrated here. Do you have a fork with your modifications ? Best, |
I think this will be fixed once #532 is merged. |
Can someone send me the full configuration steps or reference files to configure SASL_SSL/LDAP in Kafka-manager ?
if you have configured in the past, please share your settings that would be really helpful! |
Hi,
I'm trying to set up a
SASL_SSL
connection to Kafka cluster (0.10.2.0
), but I'm getting an error messageorg.apache.kafka.common.KafkaException: Failed to construct kafka consumer
which is the underlying problem for kafka-manager to display consumers information.Anyways, this is what I have:
~/jaas.conf:
conf/consumer.properties:
This how I start the service:
And that's what I'm getting in the log:
I'd appreciate help with it and I'm happy to provide some documentation to the project once we know what the problem is.
The text was updated successfully, but these errors were encountered: