From 54f98dae7bfb6b50eb9156b39d0dc2c4b8f105df Mon Sep 17 00:00:00 2001 From: Diptanu Choudhury Date: Fri, 4 Nov 2016 17:22:22 -0700 Subject: [PATCH] Fixed docs --- website/source/docs/agent/configuration/vault.html.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/website/source/docs/agent/configuration/vault.html.md b/website/source/docs/agent/configuration/vault.html.md index 9f27e420c..90dd271c7 100644 --- a/website/source/docs/agent/configuration/vault.html.md +++ b/website/source/docs/agent/configuration/vault.html.md @@ -39,11 +39,10 @@ vault { given in the format `protocol://host:port`. If your Vault installation is behind a load balancer, this should be the address of the load balancer. -- `allow_unauthenticated` `(bool: false)` - Specifies if users submitting jobs - to the Nomad server should be required to provide their own Vault token, - proving they have access to the policies listed in the job. This option should - only ever be enabled in a trusted environment, because, if enabled, users - could escalate privilege in a job. +- `allow_unauthenticated` `(bool: true)` - Specifies if users submitting jobs to + the Nomad server should be required to provide their own Vault token, proving + they have access to the policies listed in the job. This option should be + disabled in an untrusted environment. - `enabled` `(bool: false)` - Specifies if the Vault integration should be activated.