Skip to content
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

Closed
madhurkumar opened this issue Apr 13, 2017 · 8 comments
Assignees
Milestone

Comments

@madhurkumar
Copy link

madhurkumar commented Apr 13, 2017

For Kafka cluster secured with Kerberos running SASL_PLAINTEXT listeners. does Burrow support keytab based authentication for connecting to Zookeeper and Kafka?

@ogg1e
Copy link

ogg1e commented Jun 16, 2017

+1 for this. Has anyone attempted to get this working?

@jamesaharrisonuk
Copy link

Hello,
It would be great :) if someone could answer this question.

Thanks

@toddpalino
Copy link
Contributor

#228 is asking for the same thing. I'll look at adding the configs in the 1.0 rewrite.

@toddpalino
Copy link
Contributor

Resolved by 1.0 rewrite

@icearn
Copy link

icearn commented Jun 22, 2018

@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?

@icearn
Copy link

icearn commented Jun 22, 2018

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

@jrevillard
Copy link

@toddpalino, @icearn, I would also like to use a keytab to connect to our broker which uses SASL_SSL.
Would it be possible to use this option ?

@jrevillard
Copy link

@toddpalino, should I open a new issue for that ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants