From 4932bbc951742057289d7aa9ab0859f943a79caf Mon Sep 17 00:00:00 2001 From: buildmaster Date: Sat, 29 Sep 2018 11:06:48 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__client_side_usage.html | 2 +- multi/multi__quick_start.html | 2 +- multi/multi__service_registry_configuration.html | 2 +- multi/multi_pr01.html | 2 +- multi/multi_spring-cloud-vault.html | 2 +- multi/multi_vault-lease-renewal.html | 2 +- multi/multi_vault.config.authentication.html | 4 ++-- multi/multi_vault.config.backends.configurer.html | 2 +- multi/multi_vault.config.backends.database-backends.html | 2 +- multi/multi_vault.config.backends.html | 2 +- multi/multi_vault.config.fail-fast.html | 2 +- multi/multi_vault.config.ssl.html | 2 +- single/spring-cloud-vault.html | 4 ++-- spring-cloud-vault.html | 2 +- 14 files changed, 16 insertions(+), 16 deletions(-) diff --git a/multi/multi__client_side_usage.html b/multi/multi__client_side_usage.html index 78174c93..7a561283 100644 --- a/multi/multi__client_side_usage.html +++ b/multi/multi__client_side_usage.html @@ -1,6 +1,6 @@ - 2. Client Side Usage
2. Client Side Usage
Prev   Next

2. Client Side Usage

To use these features in an application, just build it as a Spring + 2. Client Side Usage

2. Client Side Usage
Prev   Next

2. Client Side Usage

To use these features in an application, just build it as a Spring Boot application that depends on spring-cloud-vault-config (e.g. see the test cases). Example Maven configuration:

Example 2.1. pom.xml

<parent>
     <groupId>org.springframework.boot</groupId>
diff --git a/multi/multi__quick_start.html b/multi/multi__quick_start.html
index bac5384d..c26bf000 100644
--- a/multi/multi__quick_start.html
+++ b/multi/multi__quick_start.html
@@ -1,6 +1,6 @@
 
       
-   1. Quick Start
1. Quick Start
Prev   Next
1. Quick Start
Prerequisites
To get started with Vault and this guide you need a
+   1. Quick Start
1. Quick Start
Prev   Next
1. Quick Start
Prerequisites
To get started with Vault and this guide you need a
 *NIX-like operating systems that provides:
  • wget, openssl and unzip
  • at least Java 7 and a properly configured JAVA_HOME environment variable
Install Vault
$ src/test/bash/install_vault.sh
Create SSL certificates for Vault
$ src/test/bash/create_certificates.sh
[Note]Note
create_certificates.sh creates certificates in work/ca and a JKS truststore work/keystore.jks. If you want to run Spring Cloud Vault using this quickstart guide you need to configure the truststore the spring.cloud.vault.ssl.trust-store property to file:work/keystore.jks.
Start Vault server
$ src/test/bash/local_run_vault.sh
Vault is started listening on 0.0.0.0:8200 using the inmem storage and
 https.
 Vault is sealed and not initialized when starting up.
[Note]Note
If you want to run tests, leave Vault uninitialized. The tests will
diff --git a/multi/multi__service_registry_configuration.html b/multi/multi__service_registry_configuration.html
index 0631a3f7..b0fb9734 100644
--- a/multi/multi__service_registry_configuration.html
+++ b/multi/multi__service_registry_configuration.html
@@ -1,6 +1,6 @@
 
       
-   7. Service Registry Configuration
7. Service Registry Configuration
Prev   Next
7. Service Registry Configuration
You can use a DiscoveryClient (such as from Spring Cloud Consul) to locate
+   7. Service Registry Configuration
7. Service Registry Configuration
Prev   Next
7. Service Registry Configuration
You can use a DiscoveryClient (such as from Spring Cloud Consul) to locate
 a Vault server by setting spring.cloud.vault.discovery.enabled=true (default false).
 The net result of that is that your apps need a bootstrap.yml (or an environment variable)
 with the appropriate discovery configuration.
diff --git a/multi/multi_pr01.html b/multi/multi_pr01.html
index a1d87121..f133b08b 100644
--- a/multi/multi_pr01.html
+++ b/multi/multi_pr01.html
@@ -1,3 +1,3 @@
 
       
-   
Prev   Next
© 2016-2018 The original authors.
[Note]Note
Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically.
Spring Cloud Vault Config provides client-side support for externalized configuration in a distributed system. With HashiCorp’s Vault you have a central place to manage external secret properties for applications across all environments. Vault can manage static and dynamic secrets such as username/password for remote applications/resources and provide credentials for external services such as MySQL, PostgreSQL, Apache Cassandra, MongoDB, Consul, AWS and more.
Prev   Next
Spring Cloud Vault Home 1. Quick Start

\ No newline at end of file
+   
Prev   Next
© 2016-2018 The original authors.
[Note]Note
Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically.
Spring Cloud Vault Config provides client-side support for externalized configuration in a distributed system. With HashiCorp’s Vault you have a central place to manage external secret properties for applications across all environments. Vault can manage static and dynamic secrets such as username/password for remote applications/resources and provide credentials for external services such as MySQL, PostgreSQL, Apache Cassandra, MongoDB, Consul, AWS and more.
Prev   Next
Spring Cloud Vault Home 1. Quick Start

\ No newline at end of file
diff --git a/multi/multi_spring-cloud-vault.html b/multi/multi_spring-cloud-vault.html
index 504088b4..40471067 100644
--- a/multi/multi_spring-cloud-vault.html
+++ b/multi/multi_spring-cloud-vault.html
@@ -1,3 +1,3 @@
 
       
-   Spring Cloud Vault
Spring Cloud Vault
   Next
Spring Cloud Vault
Table of Contents
1. Quick Start
2. Client Side Usage
2.1. Authentication
3. Authentication methods
3.1. Token authentication
3.2. AppId authentication
3.2.1. Custom UserId
3.3. AppRole authentication
3.4. AWS-EC2 authentication
3.5. AWS-IAM authentication
3.6. TLS certificate authentication
3.7. Cubbyhole authentication
3.8. Kubernetes authentication
4. Secret Backends
4.1. Generic Backend
4.2. Versioned Key-Value Backend
4.3. Consul
4.4. RabbitMQ
4.5. AWS
5. Database backends
5.1. Database
5.2. Apache Cassandra
5.3. MongoDB
5.4. MySQL
5.5. PostgreSQL
6. Configure PropertySourceLocator behavior
7. Service Registry Configuration
8. Vault Client Fail Fast
9. Vault Client SSL configuration
10. Lease lifecycle management (renewal and revocation)
   Next
   

\ No newline at end of file
+   Spring Cloud Vault
Spring Cloud Vault
   Next
Spring Cloud Vault
Table of Contents
1. Quick Start
2. Client Side Usage
2.1. Authentication
3. Authentication methods
3.1. Token authentication
3.2. AppId authentication
3.2.1. Custom UserId
3.3. AppRole authentication
3.4. AWS-EC2 authentication
3.5. AWS-IAM authentication
3.6. TLS certificate authentication
3.7. Cubbyhole authentication
3.8. Kubernetes authentication
4. Secret Backends
4.1. Generic Backend
4.2. Versioned Key-Value Backend
4.3. Consul
4.4. RabbitMQ
4.5. AWS
5. Database backends
5.1. Database
5.2. Apache Cassandra
5.3. MongoDB
5.4. MySQL
5.5. PostgreSQL
6. Configure PropertySourceLocator behavior
7. Service Registry Configuration
8. Vault Client Fail Fast
9. Vault Client SSL configuration
10. Lease lifecycle management (renewal and revocation)
   Next
   

\ No newline at end of file
diff --git a/multi/multi_vault-lease-renewal.html b/multi/multi_vault-lease-renewal.html
index e5fcbbb8..7b7255f8 100644
--- a/multi/multi_vault-lease-renewal.html
+++ b/multi/multi_vault-lease-renewal.html
@@ -1,6 +1,6 @@
 
       
-   10. Lease lifecycle management (renewal and revocation)
10. Lease lifecycle management (renewal and revocation)
Prev   
10. Lease lifecycle management (renewal and revocation)
With every secret, Vault creates a lease:
+   10. Lease lifecycle management (renewal and revocation)
10. Lease lifecycle management (renewal and revocation)
Prev   
10. Lease lifecycle management (renewal and revocation)
With every secret, Vault creates a lease:
 metadata containing information such as a time duration,
 renewability, and more.
Vault promises that the data will be valid for the given duration,
 or Time To Live (TTL). Once the lease is expired, Vault can
diff --git a/multi/multi_vault.config.authentication.html b/multi/multi_vault.config.authentication.html
index 84357e54..b2058a21 100644
--- a/multi/multi_vault.config.authentication.html
+++ b/multi/multi_vault.config.authentication.html
@@ -1,6 +1,6 @@
 
       
-   3. Authentication methods
3. Authentication methods
Prev   Next
3. Authentication methods
Different organizations have different requirements for security
+   3. Authentication methods
3. Authentication methods
Prev   Next
3. Authentication methods
Different organizations have different requirements for security
 and authentication. Vault reflects that need by shipping multiple authentication
 methods. Spring Cloud Vault supports token and AppId authentication.
3.1 Token authentication
Tokens are the core method for authentication within Vault.
 Token authentication requires a static token to be provided using the
@@ -55,7 +55,7 @@ AppRole authentication consists of two hard to guess (secret) tokens: RoleId and
 Spring Vault will not look up these or create a custom SecretId.
Example 3.6. bootstrap.yml with AppRole authentication properties
spring.cloud.vault:
     authentication: APPROLE
     app-role:
-        role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52

The following scenarios are supported along the required configuration details:
Table 3.1. Configuration
Method
RoleId
SecretId
RoleName
Token
Provided RoleId/SecretId
Provided
Provided
  
Provided RoleId without SecretId
Provided
   
Provided RoleId, Pull SecretId
Provided
Provided
Provided
Provided
Pull RoleId, provided SecretId
 
Provided
Provided
Provided
Full Pull Mode
  
Provided
Provided
Wrapped
   
Provided
Wrapped RoleId, provided SecretId
Provided
  
Provided
Provided RoleId, wrapped SecretId
 
Provided
 
Provided

Table 3.2. Pull/Push/Wrapped Matrix
RoleId
SecretId
Supported
Provided
Provided
✅
Provided
Pull
✅
Provided
Wrapped
✅
Provided
Absent
✅
Pull
Provided
✅
Pull
Pull
✅
Pull
Wrapped
❌
Pull
Absent
❌
Wrapped
Provided
✅
Wrapped
Pull
❌
Wrapped
Wrapped
✅
Wrapped
Absent
❌

[Note]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]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.
Example 3.7. bootstrap.yml with all AppRole authentication properties
spring.cloud.vault:
+        role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52

The following scenarios are supported along the required configuration details:
Table 3.1. Configuration
Method
RoleId
SecretId
RoleName
Token
Provided RoleId/SecretId
Provided
Provided
  
Provided RoleId without SecretId
Provided
   
Provided RoleId, Pull SecretId
Provided
Provided
Provided
Provided
Pull RoleId, provided SecretId
 
Provided
Provided
Provided
Full Pull Mode
  
Provided
Provided
Wrapped
   
Provided
Wrapped RoleId, provided SecretId
Provided
  
Provided
Provided RoleId, wrapped SecretId
 
Provided
 
Provided

Table 3.2. Pull/Push/Wrapped Matrix
RoleId
SecretId
Supported
Provided
Provided
✅
Provided
Pull
✅
Provided
Wrapped
✅
Provided
Absent
✅
Pull
Provided
✅
Pull
Pull
✅
Pull
Wrapped
❌
Pull
Absent
❌
Wrapped
Provided
✅
Wrapped
Pull
❌
Wrapped
Wrapped
✅
Wrapped
Absent
❌

[Note]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]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.
Example 3.7. bootstrap.yml with all AppRole authentication properties
spring.cloud.vault:
     authentication: APPROLE
     app-role:
         role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52
diff --git a/multi/multi_vault.config.backends.configurer.html b/multi/multi_vault.config.backends.configurer.html
index feecb534..996aa2c4 100644
--- a/multi/multi_vault.config.backends.configurer.html
+++ b/multi/multi_vault.config.backends.configurer.html
@@ -1,6 +1,6 @@
 
       
-   6. Configure PropertySourceLocator behavior
6. Configure PropertySourceLocator behavior
Prev   Next
6. Configure PropertySourceLocator behavior
Spring Cloud Vault uses property-based configuration to create PropertySources
+   6. Configure PropertySourceLocator behavior
6. Configure PropertySourceLocator behavior
Prev   Next
6. Configure PropertySourceLocator behavior
Spring Cloud Vault uses property-based configuration to create PropertySources
 for generic and discovered secret backends.
Discovered backends provide VaultSecretBackendDescriptor beans to describe the configuration
 state to use secret backend as PropertySource. A SecretBackendMetadataFactory is required
 to create a SecretBackendMetadata object which contains path, name and property transformation
diff --git a/multi/multi_vault.config.backends.database-backends.html b/multi/multi_vault.config.backends.database-backends.html
index 18b6c9b3..1c0edb00 100644
--- a/multi/multi_vault.config.backends.database-backends.html
+++ b/multi/multi_vault.config.backends.database-backends.html
@@ -1,6 +1,6 @@
 
       
-   5. Database backends
5. Database backends
Prev   Next
5. Database backends
Vault supports several database secret backends to generate database
+   5. Database backends
5. Database backends
Prev   Next
5. Database backends
Vault supports several database secret backends to generate database
 credentials dynamically based on configured roles. This means
 services that need to access a database no longer need to configure
 credentials: they can request them from Vault, and use Vault’s leasing
diff --git a/multi/multi_vault.config.backends.html b/multi/multi_vault.config.backends.html
index 01aca5fd..557d8829 100644
--- a/multi/multi_vault.config.backends.html
+++ b/multi/multi_vault.config.backends.html
@@ -1,6 +1,6 @@
 
       
-   4. Secret Backends
4. Secret Backends
Prev   Next
4. Secret Backends
4.1 Generic Backend
Spring Cloud Vault supports at the basic level the generic secret
+   4. Secret Backends
4. Secret Backends
Prev   Next
4. Secret Backends
4.1 Generic Backend
Spring Cloud Vault supports at the basic level the generic secret
 backend. The generic secret backend allows storage of arbitrary
 values as key-value store. A single context can store one or many
 key-value tuples. Contexts can be organized hierarchically.
diff --git a/multi/multi_vault.config.fail-fast.html b/multi/multi_vault.config.fail-fast.html
index 690bfc29..6272e366 100644
--- a/multi/multi_vault.config.fail-fast.html
+++ b/multi/multi_vault.config.fail-fast.html
@@ -1,6 +1,6 @@
 
       
-   8. Vault Client Fail Fast
8. Vault Client Fail Fast
Prev   Next
8. Vault Client Fail Fast
In some cases, it may be desirable to fail startup of a service if
+   8. Vault Client Fail Fast
8. Vault Client Fail Fast
Prev   Next
8. Vault Client Fail Fast
In some cases, it may be desirable to fail startup of a service if
 it cannot connect to the Vault Server.  If this is the desired
 behavior, set the bootstrap configuration property
 spring.cloud.vault.fail-fast=true and the client will halt with
diff --git a/multi/multi_vault.config.ssl.html b/multi/multi_vault.config.ssl.html
index cd4e69ed..b628a1b0 100644
--- a/multi/multi_vault.config.ssl.html
+++ b/multi/multi_vault.config.ssl.html
@@ -1,6 +1,6 @@
 
       
-   9. Vault Client SSL configuration
9. Vault Client SSL configuration
Prev   Next
9. Vault Client SSL configuration
SSL can be configured declaratively by setting various properties.
+   9. Vault Client SSL configuration
9. Vault Client SSL configuration
Prev   Next
9. Vault Client SSL configuration
SSL can be configured declaratively by setting various properties.
 You can set either javax.net.ssl.trustStore to configure
 JVM-wide SSL settings or spring.cloud.vault.ssl.trust-store
 to set SSL settings only for Spring Cloud Vault Config.
spring.cloud.vault:
diff --git a/single/spring-cloud-vault.html b/single/spring-cloud-vault.html
index b6a736b7..0463bfaf 100644
--- a/single/spring-cloud-vault.html
+++ b/single/spring-cloud-vault.html
@@ -1,6 +1,6 @@
 
       
-   Spring Cloud Vault
Spring Cloud Vault
Table of Contents
1. Quick Start
2. Client Side Usage
2.1. Authentication
3. Authentication methods
3.1. Token authentication
3.2. AppId authentication
3.2.1. Custom UserId
3.3. AppRole authentication
3.4. AWS-EC2 authentication
3.5. AWS-IAM authentication
3.6. TLS certificate authentication
3.7. Cubbyhole authentication
3.8. Kubernetes authentication
4. Secret Backends
4.1. Generic Backend
4.2. Versioned Key-Value Backend
4.3. Consul
4.4. RabbitMQ
4.5. AWS
5. Database backends
5.1. Database
5.2. Apache Cassandra
5.3. MongoDB
5.4. MySQL
5.5. PostgreSQL
6. Configure PropertySourceLocator behavior
7. Service Registry Configuration
8. Vault Client Fail Fast
9. Vault Client SSL configuration
10. Lease lifecycle management (renewal and revocation)
© 2016-2018 The original authors.
[Note]Note
Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically.
Spring Cloud Vault Config provides client-side support for externalized configuration in a distributed system. With HashiCorp’s Vault you have a central place to manage external secret properties for applications across all environments. Vault can manage static and dynamic secrets such as username/password for remote applications/resources and provide credentials for external services such as MySQL, PostgreSQL, Apache Cassandra, MongoDB, Consul, AWS and more.
1. Quick Start
Prerequisites
To get started with Vault and this guide you need a
+   Spring Cloud Vault
Spring Cloud Vault
Table of Contents
1. Quick Start
2. Client Side Usage
2.1. Authentication
3. Authentication methods
3.1. Token authentication
3.2. AppId authentication
3.2.1. Custom UserId
3.3. AppRole authentication
3.4. AWS-EC2 authentication
3.5. AWS-IAM authentication
3.6. TLS certificate authentication
3.7. Cubbyhole authentication
3.8. Kubernetes authentication
4. Secret Backends
4.1. Generic Backend
4.2. Versioned Key-Value Backend
4.3. Consul
4.4. RabbitMQ
4.5. AWS
5. Database backends
5.1. Database
5.2. Apache Cassandra
5.3. MongoDB
5.4. MySQL
5.5. PostgreSQL
6. Configure PropertySourceLocator behavior
7. Service Registry Configuration
8. Vault Client Fail Fast
9. Vault Client SSL configuration
10. Lease lifecycle management (renewal and revocation)
© 2016-2018 The original authors.
[Note]Note
Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically.
Spring Cloud Vault Config provides client-side support for externalized configuration in a distributed system. With HashiCorp’s Vault you have a central place to manage external secret properties for applications across all environments. Vault can manage static and dynamic secrets such as username/password for remote applications/resources and provide credentials for external services such as MySQL, PostgreSQL, Apache Cassandra, MongoDB, Consul, AWS and more.
1. Quick Start
Prerequisites
To get started with Vault and this guide you need a
 *NIX-like operating systems that provides:
  • wget, openssl and unzip
  • at least Java 7 and a properly configured JAVA_HOME environment variable
Install Vault
$ src/test/bash/install_vault.sh
Create SSL certificates for Vault
$ src/test/bash/create_certificates.sh
[Note]Note
create_certificates.sh creates certificates in work/ca and a JKS truststore work/keystore.jks. If you want to run Spring Cloud Vault using this quickstart guide you need to configure the truststore the spring.cloud.vault.ssl.trust-store property to file:work/keystore.jks.
Start Vault server
$ src/test/bash/local_run_vault.sh
Vault is started listening on 0.0.0.0:8200 using the inmem storage and
 https.
 Vault is sealed and not initialized when starting up.
[Note]Note
If you want to run tests, leave Vault uninitialized. The tests will
@@ -152,7 +152,7 @@ AppRole authentication consists of two hard to guess (secret) tokens: RoleId and
 Spring Vault will not look up these or create a custom SecretId.
Example 3.6. bootstrap.yml with AppRole authentication properties
spring.cloud.vault:
     authentication: APPROLE
     app-role:
-        role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52

The following scenarios are supported along the required configuration details:
Table 3.1. Configuration
Method
RoleId
SecretId
RoleName
Token
Provided RoleId/SecretId
Provided
Provided
  
Provided RoleId without SecretId
Provided
   
Provided RoleId, Pull SecretId
Provided
Provided
Provided
Provided
Pull RoleId, provided SecretId
 
Provided
Provided
Provided
Full Pull Mode
  
Provided
Provided
Wrapped
   
Provided
Wrapped RoleId, provided SecretId
Provided
  
Provided
Provided RoleId, wrapped SecretId
 
Provided
 
Provided

Table 3.2. Pull/Push/Wrapped Matrix
RoleId
SecretId
Supported
Provided
Provided
✅
Provided
Pull
✅
Provided
Wrapped
✅
Provided
Absent
✅
Pull
Provided
✅
Pull
Pull
✅
Pull
Wrapped
❌
Pull
Absent
❌
Wrapped
Provided
✅
Wrapped
Pull
❌
Wrapped
Wrapped
✅
Wrapped
Absent
❌

[Note]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]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.
Example 3.7. bootstrap.yml with all AppRole authentication properties
spring.cloud.vault:
+        role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52

The following scenarios are supported along the required configuration details:
Table 3.1. Configuration
Method
RoleId
SecretId
RoleName
Token
Provided RoleId/SecretId
Provided
Provided
  
Provided RoleId without SecretId
Provided
   
Provided RoleId, Pull SecretId
Provided
Provided
Provided
Provided
Pull RoleId, provided SecretId
 
Provided
Provided
Provided
Full Pull Mode
  
Provided
Provided
Wrapped
   
Provided
Wrapped RoleId, provided SecretId
Provided
  
Provided
Provided RoleId, wrapped SecretId
 
Provided
 
Provided

Table 3.2. Pull/Push/Wrapped Matrix
RoleId
SecretId
Supported
Provided
Provided
✅
Provided
Pull
✅
Provided
Wrapped
✅
Provided
Absent
✅
Pull
Provided
✅
Pull
Pull
✅
Pull
Wrapped
❌
Pull
Absent
❌
Wrapped
Provided
✅
Wrapped
Pull
❌
Wrapped
Wrapped
✅
Wrapped
Absent
❌

[Note]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]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.
Example 3.7. bootstrap.yml with all AppRole authentication properties
spring.cloud.vault:
     authentication: APPROLE
     app-role:
         role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52
diff --git a/spring-cloud-vault.html b/spring-cloud-vault.html
index 419ea5cf..a93d5f7b 100644
--- a/spring-cloud-vault.html
+++ b/spring-cloud-vault.html
@@ -4,7 +4,7 @@
 
 
 
-
+
 spring-cloud-vault