SpringCloud/spring-cloud-vault
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Sync docs from master to gh-pages

Browse Source
This commit is contained in:
buildmaster
2020-04-02 13:10:47 +00:00
parent 3d8ca00bd1
commit de04998045
5 changed files with 565 additions and 757 deletions
Download Patch File Download Diff File Expand all files Collapse all files

56
reference/html/quickstart.html
View File

@@ -129,8 +129,7 @@ $(globalSwitch);
<p><strong>Prerequisites</strong></p>
</div>
<div class="paragraph">
<p>To get started with Vault and this guide you need a
*NIX-like operating systems that provides:</p>
<p>To get started with Vault and this guide you need a *NIX-like operating systems that provides:</p>
</div>
<div class="ulist">
<ul>
@@ -149,7 +148,8 @@ $(globalSwitch);
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
This guide explains Vault setup from a Spring Cloud Vault perspective for integration testing. You can find a getting started guide directly on the Vault project site: <a href="https://learn.hashicorp.com/vault" class="bare">https://learn.hashicorp.com/vault</a>
This guide explains Vault setup from a Spring Cloud Vault perspective for integration testing.
You can find a getting started guide directly on the Vault project site: <a href="https://learn.hashicorp.com/vault" class="bare">https://learn.hashicorp.com/vault</a>
</td>
</tr>
</table>
@@ -204,7 +204,8 @@ These steps can be achieved by downloading and running <a href="https://github.c
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
<a href="https://github.com/spring-cloud/spring-cloud-vault/blob/master/src/test/bash/"><code>create_certificates.sh</code></a> creates certificates in <code>work/ca</code> and a JKS truststore <code>work/keystore.jks</code>. If you want to run Spring Cloud Vault using this quickstart guide you need to configure the truststore the <code>spring.cloud.vault.ssl.trust-store</code> property to <code>file:work/keystore.jks</code>.
<a href="https://github.com/spring-cloud/spring-cloud-vault/blob/master/src/test/bash/"><code>create_certificates.sh</code></a> creates certificates in <code>work/ca</code> and a JKS truststore <code>work/keystore.jks</code>.
If you want to run Spring Cloud Vault using this quickstart guide you need to configure the truststore the <code>spring.cloud.vault.ssl.trust-store</code> property to <code>file:work/keystore.jks</code>.
</td>
</tr>
</table>
@@ -257,8 +258,8 @@ Vault is sealed and not initialized when starting up.</p>
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
If you want to run tests, leave Vault uninitialized. The tests will
initialize Vault and create a root token <code>00000000-0000-0000-0000-000000000000</code>.
If you want to run tests, leave Vault uninitialized.
The tests will initialize Vault and create a root token <code>00000000-0000-0000-0000-000000000000</code>.
</td>
</tr>
</table>
@@ -296,8 +297,9 @@ your Vault will remain permanently sealed.</code></pre>
</div>
<div class="paragraph">
<p>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 <code>VAULT_TOKEN</code>
environment variable.</p>
Pick 3 keys and unseal Vault.
Store the Vault token in the <code>VAULT_TOKEN</code>
environment variable.</p>
</div>
<div class="listingblock">
<div class="content">
@@ -310,8 +312,8 @@ $ vault token-create -id="00000000-0000-0000-0000-000000000000" -policy="root"</
</div>
</div>
<div class="paragraph">
<p>Spring Cloud Vault accesses different resources. By default, the secret
backend is enabled which accesses secret config settings via JSON endpoints.</p>
<p>Spring Cloud Vault accesses different resources.
By default, the secret backend is enabled which accesses secret config settings via JSON endpoints.</p>
</div>
<div class="paragraph">
<p>The HTTP service has resources in the form:</p>
@@ -326,10 +328,8 @@ backend is enabled which accesses secret config settings via JSON endpoints.</p>
</div>
<div class="paragraph">
<p>where the "application" is injected as the <code>spring.application.name</code> in the
<code>SpringApplication</code> (i.e. what is normally "application" in a regular
Spring Boot app), "profile" is an active profile (or comma-separated
list of properties). Properties retrieved from Vault will be used "as-is"
without further prefixing of the property names.</p>
<code>SpringApplication</code> (i.e. what is normally "application" in a regular Spring Boot app), "profile" is an active profile (or comma-separated list of properties).
Properties retrieved from Vault will be used "as-is" without further prefixing of the property names.</p>
</div>
</div>
</div>
@@ -337,9 +337,8 @@ without further prefixing of the property names.</p>
<h2 id="_client_side_usage"><a class="link" href="#_client_side_usage">Client Side Usage</a></h2>
<div class="sectionbody">
<div class="paragraph">
<p>To use these features in an application, just build it as a Spring
Boot application that depends on <code>spring-cloud-vault-config</code> (e.g. see
the test cases). Example Maven configuration:</p>
<p>To use these features in an application, just build it as a Spring Boot application that depends on <code>spring-cloud-vault-config</code> (e.g. see the test cases).
Example Maven configuration:</p>
</div>
<div class="exampleblock">
<div class="title">Example 1. pom.xml</div>
@@ -405,11 +404,8 @@ public class Application {
</div>
</div>
<div class="paragraph">
<p>When it runs it will pick up the external configuration from the
default local Vault server on port <code>8200</code> if it is running. To modify
the startup behavior you can change the location of the Vault server
using <code>bootstrap.properties</code> (like <code>application.properties</code> but for
the bootstrap phase of an application context), e.g.</p>
<p>When it runs it will pick up the external configuration from the default local Vault server on port <code>8200</code> if it is running.
To modify the startup behavior you can change the location of the Vault server using <code>bootstrap.properties</code> (like <code>application.properties</code> but for the bootstrap phase of an application context), e.g.</p>
</div>
<div class="exampleblock">
<div class="title">Example 2. bootstrap.yml</div>
@@ -432,8 +428,8 @@ the bootstrap phase of an application context), e.g.</p>
<div class="ulist">
<ul>
<li>
<p><code>host</code> sets the hostname of the Vault host. The host name will be used
for SSL certificate validation</p>
<p><code>host</code> sets the hostname of the Vault host.
The host name will be used for SSL certificate validation</p>
</li>
<li>
<p><code>port</code> sets the Vault port</p>
@@ -457,15 +453,13 @@ Supported schemes are <code>http</code> and <code>https</code>.</p>
</ul>
</div>
<div class="paragraph">
<p>Enabling further integrations requires additional dependencies and
configuration. Depending on how you have set up Vault you might need
additional configuration like
<p>Enabling further integrations requires additional dependencies and configuration.
Depending on how you have set up Vault you might need additional configuration like
<a href="https://cloud.spring.io/spring-cloud-vault/spring-cloud-vault.html#vault.config.ssl">SSL</a> and
<a href="https://cloud.spring.io/spring-cloud-vault/spring-cloud-vault.html#vault.config.authentication">authentication</a>.</p>
</div>
<div class="paragraph">
<p>If the application imports the <code>spring-boot-starter-actuator</code> project, the
status of the vault server will be available via the <code>/health</code> endpoint.</p>
<p>If the application imports the <code>spring-boot-starter-actuator</code> project, the status of the vault server will be available via the <code>/health</code> endpoint.</p>
</div>
<div class="paragraph">
<p>The vault health indicator can be enabled or disabled through the property <code>management.health.vault.enabled</code> (default to <code>true</code>).</p>
@@ -499,7 +493,9 @@ status of the vault server will be available via the <code>/health</code> endpoi
<i class="fa icon-warning" title="Warning"></i>
</td>
<td class="content">
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.
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.
</td>
</tr>
</table>