From fd4b5a45854cf22c9a4d51eca4de510e7bdf6c9f Mon Sep 17 00:00:00 2001
From: buildmaster
Spring Cloud Vault integrates with these backends:
Using a database secret backend requires to enable the
backend in the configuration and the spring-cloud-vault-config-databases
-dependency.
Example 5.1. pom.xml
<dependencies> +dependency.Vault ships since 0.7.1 with a dedicated
databasesecret backend that allows +database integration via plugins. You can use that specific backend by adapting +one of the JDBC database properties above. Make sure to specify the appropriate +backend path, e.g.spring.cloud.vault.mysql.role.backend=database.Example 5.1. pom.xml
<dependencies> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> diff --git a/single/spring-cloud-vault.html b/single/spring-cloud-vault.html index 3d3745f5..c7a9857c 100644 --- a/single/spring-cloud-vault.html +++ b/single/spring-cloud-vault.html @@ -290,7 +290,10 @@ services that need to access a database no longer need to configure credentials: they can request them from Vault, and use Vault’s leasing mechanism to more easily roll keys.Spring Cloud Vault integrates with these backends:
Using a database secret backend requires to enable the backend in the configuration and the
spring-cloud-vault-config-databases-dependency.Example 5.1. pom.xml
<dependencies> +dependency.Vault ships since 0.7.1 with a dedicated
databasesecret backend that allows +database integration via plugins. You can use that specific backend by adapting +one of the JDBC database properties above. Make sure to specify the appropriate +backend path, e.g.spring.cloud.vault.mysql.role.backend=database.