acl: disallow leading /
on variable paths
#23757
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The path for a Variable never begins with a leading
/
, because it's stripped off in the API before it ever gets to the state store. The CLI and UI allow the leading/
for convenience, but this can be misleading when it comes to writing ACL policies. An ACL policy with a path starting with a leading/
will never match.Update the ACL policy parser so that we prevent an incorrect variable path in the policy.
Fixes: #23730