diff --git a/2.1.x/multi/multi__client_side_usage.html b/2.1.x/multi/multi__client_side_usage.html index d00416b8..5be05077 100644 --- a/2.1.x/multi/multi__client_side_usage.html +++ b/2.1.x/multi/multi__client_side_usage.html @@ -60,7 +60,7 @@ for SSL certificate validation
  • po 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 additional configuration like -SSL and -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 management.health.vault.enabled (default to 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:
+SSL and
+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 management.health.vault.enabled (default to 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 diff --git a/2.1.x/single/spring-cloud-vault.html b/2.1.x/single/spring-cloud-vault.html index 80a0720e..65981570 100644 --- a/2.1.x/single/spring-cloud-vault.html +++ b/2.1.x/single/spring-cloud-vault.html @@ -94,9 +94,9 @@ for SSL certificate validation
  • po 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 additional configuration like -SSL and -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 management.health.vault.enabled (default to 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:
+SSL and
+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 management.health.vault.enabled (default to 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 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.