You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description DEFAULT_TLS_CERT_PATH is currently defaulted to ./certs which means that CA certs have to be manually added in order to communicate with the target system.
Suggestions for an improvement
On most Linux or containerized systems, the system-wide trust store is stored at /etc/ssl/certs/ca-certificates.crt and therefore it makes sense to default to this value so that the Python client may work out of the box. By defaulting to ./certs it guarantees it will never work out of the box without a user manually creating a truststore.
If a user requires a custom trust store or is running on Windows or another Linux distribution, they still have the option of specifying the trust store location using the pravega_client_tls_cert_path environment variable.
The text was updated successfully, but these errors were encountered:
Problem description
DEFAULT_TLS_CERT_PATH
is currently defaulted to./certs
which means that CA certs have to be manually added in order to communicate with the target system.Problem location
pravega-client-rust/config/src/lib.rs
Line 49 in b57b2ea
Suggestions for an improvement
On most Linux or containerized systems, the system-wide trust store is stored at
/etc/ssl/certs/ca-certificates.crt
and therefore it makes sense to default to this value so that the Python client may work out of the box. By defaulting to./certs
it guarantees it will never work out of the box without a user manually creating a truststore.If a user requires a custom trust store or is running on Windows or another Linux distribution, they still have the option of specifying the trust store location using the
pravega_client_tls_cert_path
environment variable.The text was updated successfully, but these errors were encountered: