CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Clarify note on VAULT_TOKEN env variable (#1026)

Browse Source 
A slight update for clarity regarding the wording of the Note regarding the recommendation of using the 'VAULT_TOKEN' environment variable as opposed to using the token parameter in the configuration file.
This commit is contained in:
Alex Harness authored and GitHub committed 2021-03-24 14:17:55 -04:00
1 parent fcbf372881
commit 79283d93ac
1 file changed
+3 -2
Download Patch File Download Diff File Expand all files Collapse all files
website/content/docs/configuration/kms/transit.mdx
+3 -2
View File
@@ -94,8 +94,9 @@ Authentication-related values must be provided, either as environment
variables or as configuration parameters.
~> **Note:** Although the configuration file allows you to pass in
`VAULT_TOKEN` as part of the KMS's parameters, it is _strongly_ recommended
to set these values via environment variables.
`token` as part of the KMS stanza's parameters, it is _strongly_ recommended
to omit the `token` parameter from the configuration file and set the
token used to authenticate to Vault via the `VAULT_TOKEN` environment variable.
The Vault token used to authenticate needs the following permissions on the
transit key: