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

Support TLS in kafka output testing #10989

Closed
jsoriano opened this issue Feb 28, 2019 · 4 comments
Closed

Support TLS in kafka output testing #10989

jsoriano opened this issue Feb 28, 2019 · 4 comments
Labels

Comments

@jsoriano
Copy link
Member

jsoriano commented Feb 28, 2019

#10834 added supoort for kafka output testing, but it doesn't support TLS. Add support for TLS too.

@botelastic
Copy link

botelastic bot commented Jul 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@botelastic botelastic bot added Stalled needs_team Indicates that the issue/PR needs a Team:* label labels Jul 8, 2020
@jsoriano jsoriano removed the Stalled label Jul 9, 2020
@jsoriano jsoriano added the Team:Elastic-Agent Label for the Agent team label May 10, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/agent (Team:Agent)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label May 10, 2021
@faec
Copy link
Contributor

faec commented Apr 4, 2022

Completed in #28971

@faec faec closed this as completed Apr 4, 2022
@joostdecock
Copy link
Contributor

joostdecock commented Nov 21, 2024

@faec You closed this as completed, but #28971 adds support for SASL/SCRAM, not for TLS.

Is it possible that was a mixup, because TLS is (still) not supported in the output test:

TLS... WARN Kafka output doesn't support TLS testing
Kafka: poc-morio-node1.redacted.com:9092...
  parse host... OK
  dns lookup... OK
  addresses: 127.0.1.1
  dial up... OK

As someone using mTLS for kafka authentication, wrongly configured certificates are a very common reason for things not working as expected, and it would be incredibly helpful if the tests could verify the TLS connection.

As such, could we perhaps re-open this issue? Because while #28971 was a great contribution, I don't think it's actually addresses this particular issue at all.

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

No branches or pull requests

4 participants