From e5dac76f5d6d176b92fbc7ce4da5fd86ca65f29d Mon Sep 17 00:00:00 2001 From: Rajat Jindal Date: Wed, 28 Mar 2018 11:41:04 -0700 Subject: [PATCH] Clarify caching of exec auth tokens (#7881) * Clarify caching of exec auth tokens * Update the wording --- docs/admin/authentication.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/admin/authentication.md b/docs/admin/authentication.md index 44d1ced588..6fe7039643 100644 --- a/docs/admin/authentication.md +++ b/docs/admin/authentication.md @@ -828,7 +828,8 @@ Kubernetes API. Optionally, this output can include the expiry of the token formatted as a RFC3339 timestamp. If an expiry is omitted, the bearer token is cached until the server responds with a 401 HTTP -status code. +status code. Note that this caching is only for the duration of process and therefore the plugin +is triggered each time the tool using the plugin is invoked. ```json {