VaultConfiguration has bug if you pass null httpClientHandler param

[kadir-olmez]

When i pass null http client handler then i got following exception .

Exception :
at Vault.Client.VaultConfiguration..ctor(String basePath, HttpClientHandler httpClientHandler, Nullable`1 timeout, RetryConfiguration retryConfiguration, RateLimitConfiguration rateLimitConfiguration, TLSConfiguration tlsConfiguration)

In the Vault Configuration class, If httpClientHandler is null then you create a HttpClientHandler and set it to this.HttpClientHandler object. And After , you are using httpClientHandler object on following lines.

this.HttpClientHandler = httpClientHandler ?? new HttpClientHandler();
//
httpClientHandler.ClientCertificates.Add((X509Certificate) this.TLSConfiguration.ClientCertificate);

[AnPucel]

Hi there! I was curious if we could get some more information with regard to this issue. Would you be able to show the code you're using to initialize the VaultConfiguration as well as the VaultClient? The HttpClientHandler is an optional value passed into the configuration. VaultAddress should be the only required value for configuration.

[kadir-olmez]

i created VaultConfiguration like following line.

VaultConfiguration config = new VaultConfiguration(address,
                    tlsConfiguration: tlsConfiguration);

[46qA64KeQOy4gu6Cls6w45aY6ICA]

I am also experiencing this issue when I supply my own non-null TlsConfig and can replicate.