VaultTlsConfig (Quarkus - Vault - Runtime 3.2.0 API)

```
public interface VaultTlsConfig
```

Method Summary

All Methods Instance Methods Abstract Methods
Modifier and Type	Method	Description
`Optional<String>`	`caCert()`	Certificate bundle used to validate TLS communications with Vault.
`Optional<Boolean>`	`skipVerify()`	Allows to bypass certificate validation on TLS communications.
`boolean`	`useKubernetesCaCert()`	If true and Vault authentication type is kubernetes, TLS will be active and the cacert path will be set to /var/run/secrets/kubernetes.io/serviceaccount/ca.crt.

- Method Detail
  - skipVerify
```
Optional<Boolean> skipVerify()
```
    Allows to bypass certificate validation on TLS communications.
    If true this will allow TLS communications with Vault, without checking the validity of the certificate presented by Vault. This is discouraged in production because it allows man in the middle type of attacks.
  - caCert
```
Optional<String> caCert()
```
    Certificate bundle used to validate TLS communications with Vault.
    The path to a pem bundle file, if TLS is required, and trusted certificates are not set through javax.net.ssl.trustStore system property.
  - useKubernetesCaCert
```
@WithDefault("true")
boolean useKubernetesCaCert()
```
    If true and Vault authentication type is kubernetes, TLS will be active and the cacert path will be set to /var/run/secrets/kubernetes.io/serviceaccount/ca.crt. If set, this setting will take precedence over property quarkus.vault.tls.ca-cert. This means that if Vault authentication type is kubernetes and we want to use quarkus.vault.tls.ca-cert or system property javax.net.ssl.trustStore, then this property should be set to false.