The cassandra backend has been deprecated in Vault 0.7.1 and
+ password-property: spring.datasource.password enabled setting this value to true enables the Database backend config usagerole sets the role name of the Database role definitionbackend sets the path of the Database mount to useusername-property sets the property name in which the Database username is storedpassword-property sets the property name in which the Database password is stored
See also: Vault Documentation: Database Secrets backend ![[Warning]](images/warning.png) | Warning |
|---|
Spring Cloud Vault does not support getting new credentials and
+configuring your DataSource with them when the maximum lease time
+has been reached. That is, if max_ttl of the Database role in Vault
+is set to 24h that means that 24 hours after your application has
+started it can no longer authenticate with the database. |
![[Note]](images/note.png) | Note |
|---|
The cassandra backend has been deprecated in Vault 0.7.1 and
it is recommended to use the database backend and mount it as cassandra. |
Spring Cloud Vault can obtain credentials for Apache Cassandra.
The integration can be enabled by setting
spring.cloud.vault.cassandra.enabled=true (default false) and
diff --git a/2.1.x/single/spring-cloud-vault.html b/2.1.x/single/spring-cloud-vault.html
index 4e2c63b0..25e8be50 100644
--- a/2.1.x/single/spring-cloud-vault.html
+++ b/2.1.x/single/spring-cloud-vault.html
@@ -423,7 +423,11 @@ You can configure the property names by setting
role: readonly
backend: database
username-property: spring.datasource.username
- password-property: spring.datasource.password enabled setting this value to true enables the Database backend config usagerole sets the role name of the Database role definitionbackend sets the path of the Database mount to useusername-property sets the property name in which the Database username is storedpassword-property sets the property name in which the Database password is stored
See also: Vault Documentation: Database Secrets backend ![[Note]](images/note.png) | Note |
|---|
The cassandra backend has been deprecated in Vault 0.7.1 and
+ password-property: spring.datasource.password enabled setting this value to true enables the Database backend config usagerole sets the role name of the Database role definitionbackend sets the path of the Database mount to useusername-property sets the property name in which the Database username is storedpassword-property sets the property name in which the Database password is stored
See also: Vault Documentation: Database Secrets backend ![[Warning]](images/warning.png) | Warning |
|---|
Spring Cloud Vault does not support getting new credentials and
+configuring your DataSource with them when the maximum lease time
+has been reached. That is, if max_ttl of the Database role in Vault
+is set to 24h that means that 24 hours after your application has
+started it can no longer authenticate with the database. |
![[Note]](images/note.png) | Note |
|---|
The cassandra backend has been deprecated in Vault 0.7.1 and
it is recommended to use the database backend and mount it as cassandra. |
Spring Cloud Vault can obtain credentials for Apache Cassandra.
The integration can be enabled by setting
spring.cloud.vault.cassandra.enabled=true (default false) and
|
|