From f70143d2d42a0edbdb0f42dfee8b806a12219f6b Mon Sep 17 00:00:00 2001 From: Mark Paluch Date: Mon, 2 Jul 2018 14:16:18 +0200 Subject: [PATCH] Document AppRole limitations using reactive configuration. See gh-222. --- docs/src/main/asciidoc/spring-cloud-vault.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/spring-cloud-vault.adoc b/docs/src/main/asciidoc/spring-cloud-vault.adoc index 9ef72987..b2807259 100644 --- a/docs/src/main/asciidoc/spring-cloud-vault.adoc +++ b/docs/src/main/asciidoc/spring-cloud-vault.adoc @@ -216,7 +216,9 @@ The following scenarios are supported along the required configuration details: | Wrapped | Absent | ❌ |=== -NOTE: You can use still all combinations of push/pull/wrapped modes by providing a configured `AppRoleAuthentication` bean within the boostrap context. Spring Cloud Vault cannot derive all possible AppRole combinations from the configuration properties. +NOTE: You can use still all combinations of push/pull/wrapped modes by providing a configured `AppRoleAuthentication` bean within the bootstrap context. Spring Cloud Vault cannot derive all possible AppRole combinations from the configuration properties. + +IMPORTANT: AppRole authentication is limited to simple pull mode using reactive infrastructure. Full pull mode is not yet supported. Using Spring Cloud Vault with the Spring WebFlux stack enables Vault's reactive auto-configuration which can be disabled by setting `spring.cloud.vault.reactive.enabled=false`. .bootstrap.yml with all AppRole authentication properties ====