Closed git-noise closed 1 year ago
Actually the BadEncoding
error has been recently referenced in rustls and potentially stems from a certificate having multiple SANs.
It seems building a rustls::client::ClientConfig
and using it via LdapConnSettings::new().set_config()
is the way to go.
Hello,
I was wondering if someone had any snippet of a working TLS example with rustls and a custom CA. I tried to add the CA to the OS certificate trust-store as well as something like the following:
With
client_tls_conf
being arustls::client::ClientConfig
that loads the CA-pem file.In both cases I am facing a
invalid peer certificate: BadEncoding
issue on an otherwise seemingly valid TLS configuration - at least according to OpenSSL, curl, or ldap-utils.Many thanks, Best