Background
Jaeger supports mTLS for GRPC interface via --query.grpc.tls.client-ca parameter.
However, JaegerRemoteSampleBuilder is not exposing the a setClientTls operation for setting the privateKey / certificate PEM, as done by other Builders, such as OtlpHttpSpanExporterBuilder.setClientTls.
Solution
Align JaegerRemoteSamplerBuilder with other Builders by providing a similar setClientTls operation.
Alternative
Ideally, all builders should also support ways for passing the key/trust store pairs rather than the raw pem files. In our solution we already have the general code for handling the conversion of pem files to keystore / truststore pairs done externally, so an overload of the setClientTls and setTrustedCertificates operations with the keystore/trustore params would come handy.
See #5211
Background
Jaeger supports mTLS for GRPC interface via
--query.grpc.tls.client-caparameter.However, JaegerRemoteSampleBuilder is not exposing the a
setClientTlsoperation for setting the privateKey / certificate PEM, as done by other Builders, such as OtlpHttpSpanExporterBuilder.setClientTls.Solution
Align JaegerRemoteSamplerBuilder with other Builders by providing a similar
setClientTlsoperation.Alternative
Ideally, all builders should also support ways for passing the key/trust store pairs rather than the raw pem files. In our solution we already have the general code for handling the conversion of pem files to keystore / truststore pairs done externally, so an overload of the
setClientTlsandsetTrustedCertificatesoperations with the keystore/trustore params would come handy.See #5211