-
Notifications
You must be signed in to change notification settings - Fork 801
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
Does burrow support Kafka broker secured with Kerberos running SASL_PLAINTEXT listeners #204
Comments
+1 for this. Has anyone attempted to get this working? |
Hello, Thanks |
#228 is asking for the same thing. I'll look at adding the configs in the 1.0 rewrite. |
Resolved by 1.0 rewrite |
@toddpalino was this problem solved? I think it's a bit different from SASL_SSL support. this question in particular is for kerberos support on SASL. I don't see our configuration option for the keytab file? |
I think currently Burrow only support SASL mechanism PLAIN login, not GSSAPI (which is kerberos). A work around is to give Burrow user a separate SASL auth; I think this may help: https://docs.confluent.io/3.0.0/kafka/sasl.html#enabling-multiple-sasl-mechanisms-in-a-broker |
@toddpalino, @icearn, I would also like to use a keytab to connect to our broker which uses SASL_SSL. |
@toddpalino, should I open a new issue for that ? |
For Kafka cluster secured with Kerberos running SASL_PLAINTEXT listeners. does Burrow support keytab based authentication for connecting to Zookeeper and Kafka?
The text was updated successfully, but these errors were encountered: