diff --git a/1.1.x/index.html b/1.1.x/index.html index 349dbd3f..aca3360d 100644 --- a/1.1.x/index.html +++ b/1.1.x/index.html @@ -90,7 +90,7 @@ $(addBlockSwitches);
-

1.1.3.BUILD-SNAPSHOT

+

1.1.4.BUILD-SNAPSHOT

diff --git a/1.1.x/multi/multi__client_side_usage.html b/1.1.x/multi/multi__client_side_usage.html index 0971d110..6ceb32e4 100644 --- a/1.1.x/multi/multi__client_side_usage.html +++ b/1.1.x/multi/multi__client_side_usage.html @@ -13,7 +13,7 @@ the test cases). Example Maven configuration:

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-vault-config</artifactId> - <version>1.1.3.BUILD-SNAPSHOT</version> + <version>1.1.4.BUILD-SNAPSHOT</version> </dependency> <dependency> <groupId>org.springframework.boot</groupId> @@ -31,11 +31,11 @@ the test cases). Example Maven configuration:

</plugins> </build> -<!-- repositories also needed for snapshots and milestones -->

Then you can create a standard Spring Boot application, like this simple HTTP server:

@SpringBootApplication
-@RestController
+<!-- repositories also needed for snapshots and milestones -->

Then you can create a standard Spring Boot application, like this simple HTTP server:

@SpringBootApplication
+@RestController
 public class Application {
 
-    @RequestMapping("/")
+    @RequestMapping("/")
     public String home() {
         return "Hello World!";
     }
@@ -49,13 +49,13 @@ the startup behavior you can change the location of the Vault server
 using bootstrap.properties (like application.properties but for
 the bootstrap phase of an application context), e.g.
Example 2.2. bootstrap.yml
spring.cloud.vault:
     host: localhost
-    port: 8200
+    port: 8200
     scheme: https
-    uri: https://localhost:8200
-    connection-timeout: 5000
-    read-timeout: 15000
+    uri: https://localhost:8200
+    connection-timeout: 5000
+    read-timeout: 15000
     config:
-        order: -10

  • host sets the hostname of the Vault host. The host name will be used
+        order: -10

Enabling further integrations requires additional dependencies and configuration. Depending on how you have set up Vault you might need @@ -64,4 +64,4 @@ additional configuration like authentication.

If the application imports the spring-boot-starter-actuator project, the status of the vault server will be available via the /health endpoint.

The vault health indicator can be enabled or disabled through the property health.vault.enabled (default true).

2.1 Authentication

Vault requires an authentication mechanism to authorize client requests.

Spring Cloud Vault supports multiple authentication mechanisms to authenticate applications with Vault.

For a quickstart, use the root token printed by the Vault initialization.

Example 2.3. bootstrap.yml

spring.cloud.vault:
-    token: 19aefa97-cccc-bbbb-aaaa-225940e63d76

[Warning]Warning

Consider carefully your security requirements. Static token authentication is fine if you want quickly get started with Vault, but a static token is not protected any further. Any disclosure to unintended parties allows Vault use with the associated token roles.

Prev   Next
1. Quick Start Home 3. Authentication methods
\ No newline at end of file + token: 19aefa97-cccc-bbbb-aaaa-225940e63d76
[Warning]Warning

Consider carefully your security requirements. Static token authentication is fine if you want quickly get started with Vault, but a static token is not protected any further. Any disclosure to unintended parties allows Vault use with the associated token roles.

Prev   Next
1. Quick Start Home 3. Authentication methods
\ No newline at end of file diff --git a/1.1.x/multi/multi__quick_start.html b/1.1.x/multi/multi__quick_start.html index bac5384d..1ea87a1b 100644 --- a/1.1.x/multi/multi__quick_start.html +++ b/1.1.x/multi/multi__quick_start.html @@ -6,24 +6,24 @@ Vault is sealed and not initialized when starting up.

[Note]Note

If you want to run tests, leave Vault uninitialized. The tests will initialize Vault and create a root token 00000000-0000-0000-0000-000000000000.

If you want to use Vault for your application or give it a try then you need to initialize it first.

$ export VAULT_ADDR="https://localhost:8200"
 $ export VAULT_SKIP_VERIFY=true # Don't do this for production
-$ vault init

You should see something like:

Key 1: 7149c6a2e16b8833f6eb1e76df03e47f6113a3288b3093faf5033d44f0e70fe701
-Key 2: 901c534c7988c18c20435a85213c683bdcf0efcd82e38e2893779f152978c18c02
-Key 3: 03ff3948575b1165a20c20ee7c3e6edf04f4cdbe0e82dbff5be49c63f98bc03a03
-Key 4: 216ae5cc3ddaf93ceb8e1d15bb9fc3176653f5b738f5f3d1ee00cd7dccbe926e04
-Key 5: b2898fc8130929d569c1677ee69dc5f3be57d7c4b494a6062693ce0b1c4d93d805
-Initial Root Token: 19aefa97-cccc-bbbb-aaaa-225940e63d76
+$ vault init

You should see something like:

Key 1: 7149c6a2e16b8833f6eb1e76df03e47f6113a3288b3093faf5033d44f0e70fe701
+Key 2: 901c534c7988c18c20435a85213c683bdcf0efcd82e38e2893779f152978c18c02
+Key 3: 03ff3948575b1165a20c20ee7c3e6edf04f4cdbe0e82dbff5be49c63f98bc03a03
+Key 4: 216ae5cc3ddaf93ceb8e1d15bb9fc3176653f5b738f5f3d1ee00cd7dccbe926e04
+Key 5: b2898fc8130929d569c1677ee69dc5f3be57d7c4b494a6062693ce0b1c4d93d805
+Initial Root Token: 19aefa97-cccc-bbbb-aaaa-225940e63d76
 
-Vault initialized with 5 keys and a key threshold of 3. Please
+Vault initialized with 5 keys and a key threshold of 3. Please
 securely distribute the above keys. When the Vault is re-sealed,
-restarted, or stopped, you must provide at least 3 of these keys
+restarted, or stopped, you must provide at least 3 of these keys
 to unseal it again.
 
-Vault does not store the master key. Without at least 3 keys,
+Vault does not store the master key. Without at least 3 keys,
 your Vault will remain permanently sealed.

Vault will initialize and return a set of unsealing keys and the root token. Pick 3 keys and unseal Vault. Store the Vault token in the VAULT_TOKEN - environment variable.

$ vault unseal (Key 1)
-$ vault unseal (Key 2)
-$ vault unseal (Key 3)
+ environment variable.
$ vault unseal (Key 1)
+$ vault unseal (Key 2)
+$ vault unseal (Key 3)
 $ export VAULT_TOKEN=(Root token)
 # Required to run Spring Cloud Vault tests after manual initialization
 $ vault token-create -id="00000000-0000-0000-0000-000000000000" -policy="root"
Spring Cloud Vault accesses different resources. By default, the secret
diff --git a/1.1.x/multi/multi_vault.config.authentication.html b/1.1.x/multi/multi_vault.config.authentication.html
index a03c3a60..da8d62d0 100644
--- a/1.1.x/multi/multi_vault.config.authentication.html
+++ b/1.1.x/multi/multi_vault.config.authentication.html
@@ -8,7 +8,7 @@ Token authentication requires a static token to be provided using the
 If a token is disclosed an unintended party gains access to Vault and
 can access secrets for the intended client.
Example 3.1. bootstrap.yml
spring.cloud.vault:
     authentication: TOKEN
-    token: 00000000-0000-0000-0000-000000000000


See also: Vault Documentation: Tokens

3.2 AppId authentication

Vault supports AppId authentication that consists of two hard to guess tokens. The AppId defaults to spring.application.name that is statically configured. @@ -44,7 +44,7 @@ obtain a token.

app-id: user-id: com.examlple.MyUserIdMechanism


Example 3.5. MyUserIdMechanism.java

public class MyUserIdMechanism implements AppIdUserIdMechanism {
 
-  @Override
+  @Override
   public String createUserId() {
     String userId = ...
     return userId;
@@ -56,11 +56,11 @@ or together with a provided SecretId (push or pull mode).
RoleId and optio
 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

  • role-id sets the RoleId.
Example 3.7. bootstrap.yml with all AppRole authentication properties
spring.cloud.vault:
+        role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52

  • role-id sets the RoleId.
Example 3.7. bootstrap.yml with all AppRole authentication properties
spring.cloud.vault:
     authentication: APPROLE
     app-role:
-        role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52
-        secret-id: 1696536f-1976-73b1-b241-0b4213908d39
+        role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52
+        secret-id: 1696536f-1976-73b1-b241-0b4213908d39
         app-auth-path: approle

  • role-id sets the RoleId.
  • secret-id sets the SecretId. SecretId can be omitted if AppRole is configured without requiring SecretId (See bind_secret_id)
  • approle-path sets the path of the approle authentication mount to use
See also: Vault Documentation: Using the AppRole auth backend

3.4 AWS-EC2 authentication

The aws-ec2 auth backend provides a secure introduction mechanism for AWS EC2 instances, allowing automated retrieval of a Vault @@ -131,7 +131,7 @@ wrapping_token_ttl: 0h10m0s wrapping_token_creation_time: 2016-09-18 20:29:48.652957077 +0200 CEST wrapped_accessor: 46b6aebb-187f-932a-26d7-4f3d86a68319


Example 3.15. bootstrap.yml

spring.cloud.vault:
     authentication: CUBBYHOLE
-    token: 397ccb93-ff6c-b17b-9389-380b01ca2645

See also:

3.8 Kubernetes authentication

Kubernetes authentication mechanism (since Vault 0.8.3) allows to authenticate with Vault using a Kubernetes Service Account Token. + token: 397ccb93-ff6c-b17b-9389-380b01ca2645


See also:

3.8 Kubernetes authentication

Kubernetes authentication mechanism (since Vault 0.8.3) allows to authenticate with Vault using a Kubernetes Service Account Token. The authentication is role based and the role is bound to a service account name and a namespace.

A file containing a JWT token for a pod’s service account is automatically mounted at /var/run/secrets/kubernetes.io/serviceaccount/token.

Example 3.16. bootstrap.yml with all Kubernetes authentication properties

spring.cloud.vault:
     authentication: KUBERNETES
     kubernetes:
diff --git a/1.1.x/multi/multi_vault.config.backends.configurer.html b/1.1.x/multi/multi_vault.config.backends.configurer.html
index feecb534..706fa0a5 100644
--- a/1.1.x/multi/multi_vault.config.backends.configurer.html
+++ b/1.1.x/multi/multi_vault.config.backends.configurer.html
@@ -9,7 +9,7 @@ Default generic and discovered backend registration is disabled if Spring Cloud
 at least one VaultConfigurer bean. You can however enable default registration with
 SecretBackendConfigurer.registerDefaultGenericSecretBackends() and SecretBackendConfigurer.registerDefaultDiscoveredSecretBackends().
public class CustomizationBean implements VaultConfigurer {
 
-    @Override
+    @Override
     public void addSecretBackends(SecretBackendConfigurer configurer) {
 
         configurer.add("secret/my-application");
diff --git a/1.1.x/multi/multi_vault.config.backends.database-backends.html b/1.1.x/multi/multi_vault.config.backends.database-backends.html
index 007e7db5..3762e5f6 100644
--- a/1.1.x/multi/multi_vault.config.backends.database-backends.html
+++ b/1.1.x/multi/multi_vault.config.backends.database-backends.html
@@ -13,7 +13,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d
     <dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-vault-config-databases</artifactId>
-        <version>1.1.3.BUILD-SNAPSHOT</version>
+        <version>1.1.4.BUILD-SNAPSHOT</version>
     </dependency>
 </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for diff --git a/1.1.x/multi/multi_vault.config.backends.html b/1.1.x/multi/multi_vault.config.backends.html index bc51d1ed..94cc8403 100644 --- a/1.1.x/multi/multi_vault.config.backends.html +++ b/1.1.x/multi/multi_vault.config.backends.html @@ -26,7 +26,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-consul</artifactId> - <version>1.1.3.BUILD-SNAPSHOT</version> + <version>1.1.4.BUILD-SNAPSHOT</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -43,7 +43,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.1.3.BUILD-SNAPSHOT</version> + <version>1.1.4.BUILD-SNAPSHOT</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -62,7 +62,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.1.3.BUILD-SNAPSHOT</version> + <version>1.1.4.BUILD-SNAPSHOT</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) diff --git a/1.1.x/single/spring-cloud-vault.html b/1.1.x/single/spring-cloud-vault.html index 4ef3891f..5fe14fa6 100644 --- a/1.1.x/single/spring-cloud-vault.html +++ b/1.1.x/single/spring-cloud-vault.html @@ -6,24 +6,24 @@ Vault is sealed and not initialized when starting up.

[Note]Note

If you want to run tests, leave Vault uninitialized. The tests will initialize Vault and create a root token 00000000-0000-0000-0000-000000000000.

If you want to use Vault for your application or give it a try then you need to initialize it first.

$ export VAULT_ADDR="https://localhost:8200"
 $ export VAULT_SKIP_VERIFY=true # Don't do this for production
-$ vault init

You should see something like:

Key 1: 7149c6a2e16b8833f6eb1e76df03e47f6113a3288b3093faf5033d44f0e70fe701
-Key 2: 901c534c7988c18c20435a85213c683bdcf0efcd82e38e2893779f152978c18c02
-Key 3: 03ff3948575b1165a20c20ee7c3e6edf04f4cdbe0e82dbff5be49c63f98bc03a03
-Key 4: 216ae5cc3ddaf93ceb8e1d15bb9fc3176653f5b738f5f3d1ee00cd7dccbe926e04
-Key 5: b2898fc8130929d569c1677ee69dc5f3be57d7c4b494a6062693ce0b1c4d93d805
-Initial Root Token: 19aefa97-cccc-bbbb-aaaa-225940e63d76
+$ vault init

You should see something like:

Key 1: 7149c6a2e16b8833f6eb1e76df03e47f6113a3288b3093faf5033d44f0e70fe701
+Key 2: 901c534c7988c18c20435a85213c683bdcf0efcd82e38e2893779f152978c18c02
+Key 3: 03ff3948575b1165a20c20ee7c3e6edf04f4cdbe0e82dbff5be49c63f98bc03a03
+Key 4: 216ae5cc3ddaf93ceb8e1d15bb9fc3176653f5b738f5f3d1ee00cd7dccbe926e04
+Key 5: b2898fc8130929d569c1677ee69dc5f3be57d7c4b494a6062693ce0b1c4d93d805
+Initial Root Token: 19aefa97-cccc-bbbb-aaaa-225940e63d76
 
-Vault initialized with 5 keys and a key threshold of 3. Please
+Vault initialized with 5 keys and a key threshold of 3. Please
 securely distribute the above keys. When the Vault is re-sealed,
-restarted, or stopped, you must provide at least 3 of these keys
+restarted, or stopped, you must provide at least 3 of these keys
 to unseal it again.
 
-Vault does not store the master key. Without at least 3 keys,
+Vault does not store the master key. Without at least 3 keys,
 your Vault will remain permanently sealed.

Vault will initialize and return a set of unsealing keys and the root token. Pick 3 keys and unseal Vault. Store the Vault token in the VAULT_TOKEN - environment variable.

$ vault unseal (Key 1)
-$ vault unseal (Key 2)
-$ vault unseal (Key 3)
+ environment variable.
$ vault unseal (Key 1)
+$ vault unseal (Key 2)
+$ vault unseal (Key 3)
 $ export VAULT_TOKEN=(Root token)
 # Required to run Spring Cloud Vault tests after manual initialization
 $ vault token-create -id="00000000-0000-0000-0000-000000000000" -policy="root"
Spring Cloud Vault accesses different resources. By default, the secret
@@ -47,7 +47,7 @@ the test cases). Example Maven configuration:
<dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-starter-vault-config</artifactId>
-        <version>1.1.3.BUILD-SNAPSHOT</version>
+        <version>1.1.4.BUILD-SNAPSHOT</version>
     </dependency>
     <dependency>
         <groupId>org.springframework.boot</groupId>
@@ -65,11 +65,11 @@ the test cases). Example Maven configuration:
</plugins>
 </build>
 
-<!-- repositories also needed for snapshots and milestones -->

Then you can create a standard Spring Boot application, like this simple HTTP server:

@SpringBootApplication
-@RestController
+<!-- repositories also needed for snapshots and milestones -->

Then you can create a standard Spring Boot application, like this simple HTTP server:

@SpringBootApplication
+@RestController
 public class Application {
 
-    @RequestMapping("/")
+    @RequestMapping("/")
     public String home() {
         return "Hello World!";
     }
@@ -83,13 +83,13 @@ the startup behavior you can change the location of the Vault server
 using bootstrap.properties (like application.properties but for
 the bootstrap phase of an application context), e.g.
Example 2.2. bootstrap.yml
spring.cloud.vault:
     host: localhost
-    port: 8200
+    port: 8200
     scheme: https
-    uri: https://localhost:8200
-    connection-timeout: 5000
-    read-timeout: 15000
+    uri: https://localhost:8200
+    connection-timeout: 5000
+    read-timeout: 15000
     config:
-        order: -10

  • host sets the hostname of the Vault host. The host name will be used
+        order: -10

  • host sets the hostname of the Vault host. The host name will be used for SSL certificate validation
  • port sets the Vault port
  • scheme setting the scheme to http will use plain HTTP. Supported schemes are http and https.
  • uri configure the Vault endpoint with an URI. Takes precedence over host/port/scheme configuration
  • connection-timeout sets the connection timeout in milliseconds
  • read-timeout sets the read timeout in milliseconds
  • config.order sets the order for the property source

Enabling further integrations requires additional dependencies and configuration. Depending on how you have set up Vault you might need @@ -98,7 +98,7 @@ additional configuration like authentication.

If the application imports the spring-boot-starter-actuator project, the status of the vault server will be available via the /health endpoint.

The vault health indicator can be enabled or disabled through the property health.vault.enabled (default true).

2.1 Authentication

Vault requires an authentication mechanism to authorize client requests.

Spring Cloud Vault supports multiple authentication mechanisms to authenticate applications with Vault.

For a quickstart, use the root token printed by the Vault initialization.

Example 2.3. bootstrap.yml

spring.cloud.vault:
-    token: 19aefa97-cccc-bbbb-aaaa-225940e63d76

[Warning]Warning

Consider carefully your security requirements. Static token authentication is fine if you want quickly get started with Vault, but a static token is not protected any further. Any disclosure to unintended parties allows Vault use with the associated token roles.

3. Authentication methods

Different organizations have different requirements for security + token: 19aefa97-cccc-bbbb-aaaa-225940e63d76


[Warning]Warning

Consider carefully your security requirements. Static token authentication is fine if you want quickly get started with Vault, but a static token is not protected any further. Any disclosure to unintended parties allows Vault use with the associated token roles.

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 @@ -106,7 +106,7 @@ Token authentication requires a static token to be provided using the If a token is disclosed an unintended party gains access to Vault and can access secrets for the intended client.

Example 3.1. bootstrap.yml

spring.cloud.vault:
     authentication: TOKEN
-    token: 00000000-0000-0000-0000-000000000000

  • authentication setting this value to TOKEN selects the Token + token: 00000000-0000-0000-0000-000000000000

  • authentication setting this value to TOKEN selects the Token authentication method
  • token sets the static token to use

See also: Vault Documentation: Tokens

3.2 AppId authentication

Vault supports AppId authentication that consists of two hard to guess tokens. The AppId defaults to spring.application.name that is statically configured. @@ -142,7 +142,7 @@ obtain a token.

app-id: user-id: com.examlple.MyUserIdMechanism


Example 3.5. MyUserIdMechanism.java

public class MyUserIdMechanism implements AppIdUserIdMechanism {
 
-  @Override
+  @Override
   public String createUserId() {
     String userId = ...
     return userId;
@@ -154,11 +154,11 @@ or together with a provided SecretId (push or pull mode).
RoleId and optio
 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

  • role-id sets the RoleId.
Example 3.7. bootstrap.yml with all AppRole authentication properties
spring.cloud.vault:
+        role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52

  • role-id sets the RoleId.
Example 3.7. bootstrap.yml with all AppRole authentication properties
spring.cloud.vault:
     authentication: APPROLE
     app-role:
-        role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52
-        secret-id: 1696536f-1976-73b1-b241-0b4213908d39
+        role-id: bde2076b-cccb-3cf0-d57e-bca7b1e83a52
+        secret-id: 1696536f-1976-73b1-b241-0b4213908d39
         app-auth-path: approle

  • role-id sets the RoleId.
  • secret-id sets the SecretId. SecretId can be omitted if AppRole is configured without requiring SecretId (See bind_secret_id)
  • approle-path sets the path of the approle authentication mount to use
See also: Vault Documentation: Using the AppRole auth backend

3.4 AWS-EC2 authentication

The aws-ec2 auth backend provides a secure introduction mechanism for AWS EC2 instances, allowing automated retrieval of a Vault @@ -229,7 +229,7 @@ wrapping_token_ttl: 0h10m0s wrapping_token_creation_time: 2016-09-18 20:29:48.652957077 +0200 CEST wrapped_accessor: 46b6aebb-187f-932a-26d7-4f3d86a68319


Example 3.15. bootstrap.yml

spring.cloud.vault:
     authentication: CUBBYHOLE
-    token: 397ccb93-ff6c-b17b-9389-380b01ca2645

See also:

3.8 Kubernetes authentication

Kubernetes authentication mechanism (since Vault 0.8.3) allows to authenticate with Vault using a Kubernetes Service Account Token. + token: 397ccb93-ff6c-b17b-9389-380b01ca2645


See also:

3.8 Kubernetes authentication

Kubernetes authentication mechanism (since Vault 0.8.3) allows to authenticate with Vault using a Kubernetes Service Account Token. The authentication is role based and the role is bound to a service account name and a namespace.

A file containing a JWT token for a pod’s service account is automatically mounted at /var/run/secrets/kubernetes.io/serviceaccount/token.

Example 3.16. bootstrap.yml with all Kubernetes authentication properties

spring.cloud.vault:
     authentication: KUBERNETES
     kubernetes:
@@ -260,7 +260,7 @@ dependency.
<dependency>
         <groupId>org.springframework.cloud</groupId>
         <artifactId>spring-cloud-vault-config-consul</artifactId>
-        <version>1.1.3.BUILD-SNAPSHOT</version>
+        <version>1.1.4.BUILD-SNAPSHOT</version>
     </dependency>
 </dependencies>

The integration can be enabled by setting spring.cloud.vault.consul.enabled=true (default false) and @@ -277,7 +277,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-rabbitmq</artifactId> - <version>1.1.3.BUILD-SNAPSHOT</version> + <version>1.1.4.BUILD-SNAPSHOT</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.rabbitmq.enabled=true (default false) @@ -296,7 +296,7 @@ dependency.

<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-aws</artifactId> - <version>1.1.3.BUILD-SNAPSHOT</version> + <version>1.1.4.BUILD-SNAPSHOT</version> </dependency> </dependencies>


The integration can be enabled by setting spring.cloud.vault.aws=true (default false) @@ -323,7 +323,7 @@ backend path, e.g. spring.cloud.vault.mysql.role.backend=d <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-vault-config-databases</artifactId> - <version>1.1.3.BUILD-SNAPSHOT</version> + <version>1.1.4.BUILD-SNAPSHOT</version> </dependency> </dependencies>

[Note]Note

Enabling multiple JDBC-compliant databases will generate credentials and store them by default in the same property keys hence property names for @@ -392,7 +392,7 @@ Default generic and discovered backend registration is disabled if Spring Cloud at least one VaultConfigurer bean. You can however enable default registration with SecretBackendConfigurer.registerDefaultGenericSecretBackends() and SecretBackendConfigurer.registerDefaultDiscoveredSecretBackends().

public class CustomizationBean implements VaultConfigurer {
 
-    @Override
+    @Override
     public void addSecretBackends(SecretBackendConfigurer configurer) {
 
         configurer.add("secret/my-application");