SpringCloud/spring-cloud-config
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
2019-12-18 21:42:43 +00:00
parent cbc9ad35b0
commit 440d6c230b
2 changed files with 42 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
reference/html/index.html
View File

@@ -1287,6 +1287,27 @@ $ vault kv put secret/myapp foo=myappsbar</code></pre>
}</code></pre>
</div>
</div>
<div class="paragraph">
<p>The default way for a client to provide the necessary authentication to let Config Server talk to Vault is to set the X-Config-Token header.
However, you can instead omit the header and configure the authentication in the server, by setting the same configuration properties as Spring Cloud Vault.
The property to set is <code>spring.cloud.config.server.vault.authentication</code>.
It should be set to one of the supported authentication methods.
You may also need to set other properties specific to the authentication method you use, by using the same property names as documented for <code>spring.cloud.vault</code> but instead using the <code>spring.cloud.config.server.vault</code> prefix.
See the <a href="https://cloud.spring.io/spring-cloud-vault/reference/html/#vault.config.authentication">Spring Cloud Vault Reference Guide</a> for more detail.</p>
</div>
<div class="admonitionblock important">
<table>
<tr>
<td class="icon">
<i class="fa icon-important" title="Important"></i>
</td>
<td class="content">
If you omit the X-Config-Token header and use a server property to set the authentication, the Config Server application needs an additional dependency on Spring Vault to enable the additional authentication options.
See the <a href="https://docs.spring.io/spring-vault/docs/current/reference/html/#dependencies">Spring Vault Reference Guide</a> for how to add that dependency.
</td>
</tr>
</table>
</div>
<div class="sect4">
<h5 id="_multiple_properties_sources"><a class="link" href="#_multiple_properties_sources">Multiple Properties Sources</a></h5>
<div class="paragraph">

21
reference/html/spring-cloud-config.html
View File

@@ -1287,6 +1287,27 @@ $ vault kv put secret/myapp foo=myappsbar</code></pre>
}</code></pre>
</div>
</div>
<div class="paragraph">
<p>The default way for a client to provide the necessary authentication to let Config Server talk to Vault is to set the X-Config-Token header.
However, you can instead omit the header and configure the authentication in the server, by setting the same configuration properties as Spring Cloud Vault.
The property to set is <code>spring.cloud.config.server.vault.authentication</code>.
It should be set to one of the supported authentication methods.
You may also need to set other properties specific to the authentication method you use, by using the same property names as documented for <code>spring.cloud.vault</code> but instead using the <code>spring.cloud.config.server.vault</code> prefix.
See the <a href="https://cloud.spring.io/spring-cloud-vault/reference/html/#vault.config.authentication">Spring Cloud Vault Reference Guide</a> for more detail.</p>
</div>
<div class="admonitionblock important">
<table>
<tr>
<td class="icon">
<i class="fa icon-important" title="Important"></i>
</td>
<td class="content">
If you omit the X-Config-Token header and use a server property to set the authentication, the Config Server application needs an additional dependency on Spring Vault to enable the additional authentication options.
See the <a href="https://docs.spring.io/spring-vault/docs/current/reference/html/#dependencies">Spring Vault Reference Guide</a> for how to add that dependency.
</td>
</tr>
</table>
</div>
<div class="sect4">
<h5 id="_multiple_properties_sources"><a class="link" href="#_multiple_properties_sources">Multiple Properties Sources</a></h5>
<div class="paragraph">