-
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
Using Client Certificate for Elastic Search Authentication #678
Comments
if the Go driver supports it, we can add the options similar to how they were added for Cassandra:
|
oh yeah thanks for update. Should we let this issue opened (in case the client updates it)? Please feel free to close it as well |
Hi @reynaldiwijaya! How did you manage that in a proper way please 😃 ? |
@yurishkuro I just saw that you are using the olivere/elastic client in Go. I just checked their docs and found it's possible: It would be really helpful using ES cluster through https 😀 Do you think it could be on the roadmap? I'm not used to Golang but if I could help by testing... it would be a pleasure 😃 |
Hi @yurishkuro any news about having this on your roadmap? Thanks :) |
Honestly, seeing as we don't use ES internally, don't get too excited about seeing this on a roadmap any time soon. |
@isaachier oh ok that's too bad 😢 Anyway, thanks for this tool 😀 ! |
If the driver supports it, the change is fairy trivial, doesn't have to be done by official maintainers. |
@sneko hi im using cassandra at the end, works like a charm 👍 |
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
* Fixed #678 Signed-off-by: Chun Lin Yang <[email protected]> * Fixed #678 Signed-off-by: Chun Lin Yang <[email protected]> * address review comments Signed-off-by: Chun Lin Yang <[email protected]> * address review comments Signed-off-by: Chun Lin Yang <[email protected]> * support timeout for non-tls-enabled case Signed-off-by: Chun Lin Yang <[email protected]> * change method name Signed-off-by: Chun Lin Yang <[email protected]>
* Fixed jaegertracing/jaeger#678 Signed-off-by: Chun Lin Yang <[email protected]> * Fixed jaegertracing/jaeger#678 Signed-off-by: Chun Lin Yang <[email protected]> * address review comments Signed-off-by: Chun Lin Yang <[email protected]> * address review comments Signed-off-by: Chun Lin Yang <[email protected]> * support timeout for non-tls-enabled case Signed-off-by: Chun Lin Yang <[email protected]> * change method name Signed-off-by: Chun Lin Yang <[email protected]>
* Fixed jaegertracing/jaeger#678 Signed-off-by: Chun Lin Yang <[email protected]> * Fixed jaegertracing/jaeger#678 Signed-off-by: Chun Lin Yang <[email protected]> * address review comments Signed-off-by: Chun Lin Yang <[email protected]> * address review comments Signed-off-by: Chun Lin Yang <[email protected]> * support timeout for non-tls-enabled case Signed-off-by: Chun Lin Yang <[email protected]> * change method name Signed-off-by: Chun Lin Yang <[email protected]>
Is there any plan to accommodate using client certificate for authenticating jaeger to ES? Our elastic search deployment is using search guard which only enable client certificate now, and we would like to keep it that way. ES is deployed in Kubernetes v1.9, and we would like to deploy Jaeger there as well.
If there are none, do you have any suggestion of workaround for this problem?
The text was updated successfully, but these errors were encountered: