-
Notifications
You must be signed in to change notification settings - Fork 2.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
Configure Jager Collector to work with Kafka With Basic Authentication #1966
Comments
Wouldn't basic auth be sent in clear text? I can see how it can be useful with HTTPS, but without TLS is sounds like an anti-pattern. But, if the sarama driver supports it, it is fairly easy to add. |
@yurishkuro |
I am picking it up if anyone haven't started. |
…jaegertracing#1966 Signed-off-by: chandresh-pancholi <[email protected]>
…rtracing#1966 Signed-off-by: chandresh-pancholi <[email protected]>
#1983) * Configure Jager Collector to work with Kafka With Basic Authentication #1966 Signed-off-by: chandresh-pancholi <[email protected]> * Changing method name from addPlainTextFlag to addPlainTextFlags #1966 Signed-off-by: chandresh-pancholi <[email protected]>
Requirement -
Looking to integrate with Kafka which is provided by a platform Service. However, the kafka service provided by the platform only supports basic authentication
Problem -
The jager documentation or options did not indicate support for Kafka basic authentication
As a result, we would not be able to integrate our Jaeger solution with existing Kafka Services provided with our platform
Proposal -
Jaeger to support authentication mechanisms provided by Kafka
Any open questions to address
Is it available? Is it documentation that I possibly missed? Or is there a reason why it was not implemented?
(Maybe some best practise that I am unaware of)
The text was updated successfully, but these errors were encountered: