From d2531ccb83d0c78b050fa86f3595b93b0935f324 Mon Sep 17 00:00:00 2001 From: Mahmood Ali Date: Mon, 27 Jan 2020 13:45:52 -0500 Subject: [PATCH] docs: reseting bootstrap doesn't invalidate token --- website/source/guides/security/acl.html.markdown | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/source/guides/security/acl.html.markdown b/website/source/guides/security/acl.html.markdown index 0d72c0e6e..fb11ebe5e 100644 --- a/website/source/guides/security/acl.html.markdown +++ b/website/source/guides/security/acl.html.markdown @@ -419,6 +419,8 @@ Error bootstrapping: Unexpected response code: 500 (Invalid bootstrap reset inde This is because the reset file is in place, but with the incorrect index. The reset file can be deleted, but Nomad will not reset the bootstrap until the index is corrected. +Resetting ACL Bootstrap does not automatically invalidate previous ACL tokens: Previous bootstrap token remains a valid, and existing tools that utilize it remain functional. If the token is unused, or if a management token is suspected of being vulnerable, then we should invalidate it, update any existing system with new tokens, and audit all existing tokens. + ## Vault Integration HashiCorp Vault has a secret backend for generating short-lived Nomad tokens. As Vault has a number of authentication backends, it could provide a workflow where a user or orchestration system authenticates using an pre-existing identity service (LDAP, Okta, Amazon IAM, etc.) in order to obtain a short-lived Nomad token.