io.quarkus.vault.runtime.config.VaultTlsConfig.jdp Maven / Gradle / Ivy
Show all versions of quarkus-vault Show documentation
#
#Fri Jun 26 02:13:17 CEST 2020
io.quarkus.vault.runtime.config.VaultTlsConfig.caCert=Certificate bundle used to validate TLS communications with Vault.\n\nThe path to a pem bundle file, if TLS is required, and trusted certificates are not set through\njavax.net.ssl.trustStore system property.
io.quarkus.vault.runtime.config.VaultTlsConfig.useKubernetesCaCert=If true and Vault authentication type is kubernetes, TLS will be active and the cacert path will\nbe set to /var/run/secrets/kubernetes.io/serviceaccount/ca.crt. If set, this setting will take precedence\nover property quarkus.vault.tls.ca-cert. This means that if Vault authentication type is kubernetes\nand we want to use quarkus.vault.tls.ca-cert or system property javax.net.ssl.trustStore, then this\nproperty should be set to false.
io.quarkus.vault.runtime.config.VaultTlsConfig.skipVerify=Allows to bypass certificate validation on TLS communications.\n
\nIf true this will allow TLS communications with Vault, without checking the validity of the\ncertificate presented by Vault. This is discouraged in production because it allows man in the middle\ntype of attacks.