-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
OpenTracing spans reveal URL auth credentials #1459
Comments
Oops. That's a bug for sure. |
This commit improves the tests to make sure that HTTP basic auth credentials don't leak into tracing data. See #1459
I improved tests in 180a7ca but cannot reproduce. Am I missing something? |
This commit improves the tests to make sure that HTTP basic auth credentials don't leak into tracing data. See olivere#1459
Great. Just to be clear, that logging goes to the OpenTracing span? |
Whoops. I'm sorry... |
Have to double-check. |
This commit hopefully, finally, fixes the credentials leakage described in #1459.
I'll give it another go in 7.0.31. It replaced the occurrence of |
Thank you! |
This commit will also redact the URL to not expose credentials, similar to #1459.
Which version of Elastic are you using?
[X] elastic.v7 (for Elasticsearch 7.x)
[ ] elastic.v6 (for Elasticsearch 6.x)
[ ] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)
Please describe the expected behavior
We expected the spans reported to hide the user name and password.
Please describe the actual behavior
Full URL was exposed. Example from Jaeger UI (scrubbed):
Any steps to reproduce the behavior?
Set the client up with a URL with a user name and password.
I'll see about creating a PR for this.
The text was updated successfully, but these errors were encountered: