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

Add SASL-SCRAM ability to Kafka connection #598

Merged
merged 1 commit into from May 11, 2020

Conversation

rjh-yext
Copy link
Contributor

@rjh-yext rjh-yext commented Jan 14, 2020

This PR adds the ability to connect to Kafka via SASL-SCRAM 256 or 512

It adds an entry in the SASL Profile configuration called
key=mechanism
value type=string
required=no
default value=(empty)
Which accepts either values SCRAM-SHA-256, SCRAM-SHA-512

Partially addresses #526

@bai
Copy link
Collaborator

bai commented Jan 15, 2020

Thanks for contributing. Could you please rebase your PR off of master and run make fmt to fix indentation bits?

This PR adds the ability to connect to Kafka via SASL-SCRAM 256 or 512

It adds an entry in the SASL Profile configuration called
key=mechanism
value type=string
required=no
default value=(empty)
Which accepts either values SCRAM-SHA-256, SCRAM-SHA-512

Partially addresses linkedin#526
@rjh-yext rjh-yext changed the title This PR adds the ability to connect to Kafka via SASL-SCRAM 256 or 512 Add SASL-SCRAM ability to Kafka connection Jan 15, 2020
Copy link

@andrewchoi5 andrewchoi5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Travis CI build is failing for continuous-integration/travis-ci/pr
please resolve.

@johnarok
Copy link

johnarok commented Mar 6, 2020

This patch worked for my setup, SCRAM + SASL + TLS, thank you @rjh-yext

@jaapterwoerds
Copy link

Thanks for your work on this PR @rjh-yext. Are you planning to make it ready to be merged into master or can somebody help you with that?

@jaapterwoerds
Copy link

jaapterwoerds commented May 11, 2020

I could provide a patch to fix the linting and merge conflicts, but I'm not sure how to go about that

@bai bai merged commit 0f67ed5 into linkedin:master May 11, 2020
@bai
Copy link
Collaborator

bai commented May 11, 2020

Thanks for contributing! Shipped with #627.

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

Successfully merging this pull request may close these issues.

None yet

5 participants