-
Notifications
You must be signed in to change notification settings - Fork 415
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
TLS settings for OtlpHttpExporter #1756
Comments
This is blocked for - #389 As of now, the our HTTP Client doesn't have provision to supply the root ca certificate (for server authentication), and client certificate chain (for client authentication) during HTTP(S) handshake.
Yes this would require a changes in OTEL specification, if you would like to initiate the discussion there. |
|
This issue was marked as stale due to lack of activity. |
I am checking how to enable TLS encryption for connection between
OtlpHttpExporter
and Otel Collector. I found that exporter should supports https endpoint address, but it does not allow to configure TLS options. As a minimum I have to specify custom root CA certificate file. I also would like to enforce TLS 1.2+ and selected ciphers. Please add such configuration options for exporter.I found that grpc exporter allows to specify path to CA certificates using
ssl_credentials_cacert_path
option orOTEL_EXPORTER_OTLP_CERTIFICATE
env var. However it also does now allow to specify minimum TLS version and ciphers list: https://github.com/open-telemetry/opentelemetry-cpp/tree/main/exporters/otlpI suspect that this may require some changes to OTEL specification too.
The text was updated successfully, but these errors were encountered: