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

Allow configuration of AWS-EC2 nonce.

Browse Source 
We now support static configuration of the AWS-EC2 authentication nonce to support re-login on application crashes/vm-internal restarts.

Closes gh-103.
This commit is contained in:
Mark Paluch
2017-05-11 17:00:52 +02:00
parent c04c6e994d
commit 03dd5e36c0
3 changed files with 20 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/src/main/asciidoc/spring-cloud-vault.adoc
View File

@@ -240,17 +240,7 @@ party does not have the nonce and can raise an alert in Vault for
further investigation.
The nonce is kept in memory and is lost during application restart.
.bootstrap.yml with disabled nonce
====
[source,yaml]
----
spring.cloud.vault:
authentication: AWS_EC2
aws-ec2:
use-nonce: false
----
====
You can configure a static nonce with `spring.cloud.vault.aws-ec2.nonce`.
AWS-EC2 authentication roles are optional and default to the AMI.
You can configure the authentication role by setting the
@@ -277,7 +267,7 @@ spring.cloud.vault:
role: application-server
aws-ec2-path: aws-ec2
identity-document: http://...
use-nonce: false
nonce: my-static-nonce
----
====
@@ -286,7 +276,7 @@ authentication method
* `role` sets the role name of the AWS EC2 role definition
* `aws-ec2-path` sets the path of the AWS EC2 mount to use
* `identity-document` sets URL of the PKCS#7 AWS EC2 identity document
* `use-nonce` setting this value to `false` will disable nonce usage
* `nonce` used for AWS-EC2 authentication. An empty nonce defaults to nonce generation
See also: https://www.vaultproject.io/docs/auth/aws-ec2.html[Vault Documentation: Using the aws-ec2 auth backend]