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: Support auth via keystore and truststore #25152

Closed
pranavmarla opened this issue Aug 10, 2023 · 7 comments
Closed

Kafka: Support auth via keystore and truststore #25152

pranavmarla opened this issue Aug 10, 2023 · 7 comments

Comments

@pranavmarla
Copy link

Component(s)

exporter/kafka, receiver/kafka

Is your feature request related to a problem? Please describe.

Currently, although the built-in Kafka console clients let you authenticate via keystore and truststore files (see here), the OTel Kafka clients (i.e. exporter and receiver) do not support that. This makes it more difficult to transition from the built-in clients to the OTel agent.

Describe the solution you'd like

The OTel Kafka clients (i.e. exporter and receiver) should have new auth settings that take in keystore and truststore files, just like the built-in Kafka clients do -- this allows you to authenticate via the keystore and truststore files.

Describe alternatives you've considered

Currently, the only way to get around this gap is to manually extract the individual key and certificates from the keystore and truststore files, and then supply those individual key and certificates to the OTel agent -- see here for an example.

Additional context

No response

@pranavmarla pranavmarla added enhancement New feature or request needs triage New item requiring triage labels Aug 10, 2023
@github-actions
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@frzifus
Copy link
Member

frzifus commented Sep 14, 2023

Sounds reasonable to me. Wdyt @MovieStoreGuy @pavolloffay ?

@pranavmarla would you like to work on this?

@pranavmarla
Copy link
Author

Thanks @frzifus! Unfortunately, I don't think I'll have time to implement this myself any time soon

Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Nov 14, 2023
@frzifus
Copy link
Member

frzifus commented Nov 14, 2023

Any update on this?

@github-actions github-actions bot removed the Stale label Nov 14, 2023
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jan 15, 2024
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2024
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

2 participants