From 418513bbd91c26eae8a84ea34c5dbd2050a3e02f Mon Sep 17 00:00:00 2001 From: Calvin Leung Huang Date: Tue, 19 Jun 2018 12:10:39 -0400 Subject: [PATCH] Be explicit about trailing slash on paths for list capability (#4793) --- website/source/docs/concepts/policies.html.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/website/source/docs/concepts/policies.html.md b/website/source/docs/concepts/policies.html.md index c45f2e9f1..b9008b20b 100644 --- a/website/source/docs/concepts/policies.html.md +++ b/website/source/docs/concepts/policies.html.md @@ -163,7 +163,8 @@ and **is not a regular expression**! When providing `list` capability, it is important to note that since listing always operates on a prefix, policies must operate on a prefix because Vault -will sanitize request paths to be prefixes: +will sanitize request paths to be prefixes. In other words, policy paths +targeting `list` capability should end with a trailing slash: ```ruby path "secret/foo" {