From 478239676257046e5075c65ca201967970047a70 Mon Sep 17 00:00:00 2001 From: hc-github-team-secure-vault-core <82990506+hc-github-team-secure-vault-core@users.noreply.github.com> Date: Mon, 10 Apr 2023 14:43:09 -0400 Subject: [PATCH] backport of commit 7b40f73646a4994308414f585eb1a492a1cc8378 (#19832) Co-authored-by: Brian Shumate --- website/content/partials/tokenstorefields.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/website/content/partials/tokenstorefields.mdx b/website/content/partials/tokenstorefields.mdx index a74b93671514..d84a94df25d0 100644 --- a/website/content/partials/tokenstorefields.mdx +++ b/website/content/partials/tokenstorefields.mdx @@ -13,9 +13,7 @@ token may be used (within its lifetime); 0 means unlimited. If you require the token to have the ability to create child tokens, you will need to set this value to 0. -- `token_period` `(integer: 0 or string: "")` - The - [period](/vault/docs/concepts/tokens#token-time-to-live-periodic-tokens-and-explicit-max-ttls), - if any, to set on the token. +- `token_period` `(integer: 0 or string: "")` - The maximum allowed [period](/vault/docs/concepts/tokens#token-time-to-live-periodic-tokens-and-explicit-max-ttls) value when a periodic token is requested from this role. - `token_type` `(string: "")` - The type of token that should be generated. Can be `service`, `batch`, or `default` to use the mount's tuned default (which unless changed will be `service` tokens). For token store roles, there are two