-
Notifications
You must be signed in to change notification settings - Fork 1.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
Add SASL_SCRAM authentication mechanism on kafka exporter #2322
Add SASL_SCRAM authentication mechanism on kafka exporter #2322
Conversation
|
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
@jpkrohling can you review this please? |
Sorry, was on a long break. Will review this one soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is missing quite a few tests, but looks like it's a good start.
097c438
to
b6211f3
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is still missing a test and the build seems to be failing, but other than that, looks sane.
acee1a1
to
1ed9d6f
Compare
Hi @jpkrohling, sorry about the delay. I've written some unit tests and changed the Authentication type from SCRAM to SASL. Maybe PlainText could be deprecated in favor of sasl.mechanism = "PLAIN". |
1ed9d6f
to
0a253e8
Compare
|
33354ac
to
0a253e8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good then, it's only missing the PLAIN in one place.
32bbbde
to
4f8d110
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't tried this PR myself as it's not that easy for me to get a properly configured Kafka instance, but once @4lt1 confirms that it was manually tested, this is ready to be merged.
@jpkrohling, It was manually tested. |
42d9d88
to
4f8d110
Compare
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
@open-telemetry/collector-maintainers, would one of you please review/merge this one? |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
@open-telemetry/collector-maintainers, would one of you please review/merge this one? I think it's only fair if you could also fix the |
@@ -48,6 +48,7 @@ require ( | |||
github.com/stretchr/testify v1.7.0 | |||
github.com/tinylib/msgp v1.1.5 | |||
github.com/uber/jaeger-lib v2.4.0+incompatible | |||
github.com/xdg-go/scram v0.0.0-20180814205039-7eeb5667e42c |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How ok are we to depend on a very old, not actively maintained package?
Does not even have go[mod/sum].
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly? It doesn't worry me that much, as the code is fairly simple and based on a couple of RFCs. Once the standard is implemented, there's not much else to do. I do have thought about the responsiveness of the author in that repository (see the issue opened by @yurishkuro) but I don't see a reason for implementing this ourselves at this moment.
|
Fix godoc comment to better explain struct proposal Co-authored-by: Juraci Paixão Kröhling <juraci.github@kroehling.de> Fix return error message format Co-authored-by: Juraci Paixão Kröhling <juraci.github@kroehling.de> Add Unit tests Change Authentication config to SASL Use SASL mechanisms as described in RFC https://tools.ietf.org/html/rfc4422#section-3.1 Add PLAIN mechanism on README documentation Fix Typo on test comment Co-authored-by: Juraci Paixão Kröhling <juraci.github@kroehling.de> Add comments on SASLConfig describing expected values
1c86efc
to
ffc1192
Compare
@4lt1 do you mind creating a new PR (just clone the branch and open a new PR) to make circleCI trigger to run the tests? Thank you, and sorry for this |
No problem at all @bogdandrutu, the new PR is #2503 |
I'm closing this in favor of #2503 |
Generated from a modified version of the v1.5.0 release of the specification using a modified version of the semconvgen tools. The specification contained capitalized IDs that caused errors from the semconvgen tool. These errors were manually resolved and the rest of the Go formatting tools were used to provide consistent code. Important to note, the Go semconvgen tooling includes new name capitalization rules for ReplicaSet, StatefulSet, and DaemonSet that mean code names are not backwards compatible. This is included in the changelog to help users perform the upgrade.
…y#2322) Bumps [go.etcd.io/etcd/client/v2](https://github.com/etcd-io/etcd) from 2.305.5 to 2.305.6. - [Release notes](https://github.com/etcd-io/etcd/releases) - [Changelog](https://github.com/etcd-io/etcd/blob/main/Dockerfile-release.amd64) - [Commits](etcd-io/etcd@client/v2.305.5...client/v2.305.6) --- updated-dependencies: - dependency-name: go.etcd.io/etcd/client/v2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Description:
This PR adds SASL/SCRAM authentication to kafka exporter and receiver.
Link to tracking Issue:
Resolves #2252
Documentation:
Added to readme