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

Kafka connection and credentials flexibility #119

Open
djones6 opened this issue Jul 1, 2020 · 0 comments
Open

Kafka connection and credentials flexibility #119

djones6 opened this issue Jul 1, 2020 · 0 comments

Comments

@djones6
Copy link
Collaborator

djones6 commented Jul 1, 2020

I noticed that the microservices hard-code the notion of using SASL PLAIN authentication, with a username of 'token', if an API key is provided (and optionally, the certificate to use to verify the server).

It appears this is sufficient for connecting to Event Streams. However, we might want to be more flexible if (for example) connecting to a Kafka created by Strimzi, which does not allow the use of PLAIN authentication (they support either mutual TLS, or SCRAM-SHA-512, which is effectively username and password).

This would require that the sasl.mechanism and username are configurable. I haven't looked at mutual TLS yet, but I imagine this would require injection of a client certificate instead of a username and password.

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

No branches or pull requests

1 participant