From efb87eafeb9bf0238329c677c1282af35b7e23e7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?M=C3=A5rten=20Svantesson?= Date: Wed, 22 May 2019 15:21:12 +0200 Subject: [PATCH] Document that database credentials are not rotated. Clarifying limitation with Spring Cloud Vault not being able to rotate database secrets Original pull request: gh-335. --- docs/src/main/asciidoc/spring-cloud-vault.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/src/main/asciidoc/spring-cloud-vault.adoc b/docs/src/main/asciidoc/spring-cloud-vault.adoc index 22bba735..ce6a23bd 100644 --- a/docs/src/main/asciidoc/spring-cloud-vault.adoc +++ b/docs/src/main/asciidoc/spring-cloud-vault.adoc @@ -998,6 +998,10 @@ spring.cloud.vault: See also: https://www.vaultproject.io/docs/secrets/databases/index.html[Vault Documentation: Database Secrets backend] +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. + [[vault.config.backends.cassandra]] === Apache Cassandra