From e6840b269ce02cbf15e29d2f4e157978542b4831 Mon Sep 17 00:00:00 2001 From: Tom Proctor Date: Mon, 25 Oct 2021 18:25:24 +0100 Subject: [PATCH] agent: Docs for auto-auth and limited-use tokens (#12918) There are a number of auth methods that support creating tokens with a limited number of uses. However, Vault Agent doesn't track the uses remaining for its auto-auth token, so it may result in flaky permission denied responses if that limit is hit and Vault Agent remains unaware. --- website/content/docs/agent/autoauth/index.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/content/docs/agent/autoauth/index.mdx b/website/content/docs/agent/autoauth/index.mdx index 6d8da059cf..1bf351e5aa 100644 --- a/website/content/docs/agent/autoauth/index.mdx +++ b/website/content/docs/agent/autoauth/index.mdx @@ -105,6 +105,12 @@ The top level `auto_auth` block has two configuration entries: ### Configuration (Method) +~> Auto-auth does not support using tokens with a limited number of uses. Vault +Agent does not track the number of uses remaining, and may allow the token to +expire before attempting to renew it. For example, if using AppRole auto-auth, +you must use 0 (meaning unlimited) as the value for +[`token_num_uses`](https://www.vaultproject.io/api-docs/auth/approle#token_num_uses). + These are common configuration values that live within the `method` block: - `type` `(string: required)` - The type of the method to use, e.g. `aws`,