From f021fffabeb0e3ad6fd64dfd0a341644c809afaa Mon Sep 17 00:00:00 2001 From: vishalnayak Date: Tue, 26 Feb 2019 10:20:55 -0500 Subject: [PATCH] Agent doc update for beta testers --- website/source/docs/agent/caching/index.html.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/website/source/docs/agent/caching/index.html.md b/website/source/docs/agent/caching/index.html.md index b757cdaaf0..0907598d6b 100644 --- a/website/source/docs/agent/caching/index.html.md +++ b/website/source/docs/agent/caching/index.html.md @@ -36,6 +36,13 @@ However, even when enabled, if requests that reach the agent already have a token attached on them, the attached token will be put to use instead of the auto-auth token. +-> **Note:** In Vault 1.1-beta, if the request doesn't already contain a Vault +token, then the `auto-auth` token will used to make requests. The resulting +secrets from these `auto-auth` token calls are not cached. They will be in the +non-beta version. To test out the caching scenarios, please make a login +request or a token creation request via the agent. The secrets generated from +these new tokens will get cached. + ## Cache Evictions The eviction of cache entries will occur when the agent fails to renew secrets.