Policy parsing bug in 0.11.0

[Garath620]

Describe the bug
Policy syntax is not accepted anymore by the latest version.

To Reproduce
Create new policy with this content :
{"path":{"secret/*":{"capabilities":["read"]}}}
Return :
"Error failed to validate policy templating: unbalanced templating characters"

To be accepted I must use this syntax :
{"path":{"secret/*":{"capabilities":["read"]} } }

Expected behavior
Accept valid json regardless of space character like 0.10.4 version

Environment:

• Vault Server Version (retrieve with vault status): 0.11.0

Additional context

KO: {"path":{"secret/*":{"capabilities":["read"]}}}
OK: {"path":{"secret/*":{"capabilities":["read"]} } }

[alitheg]

I also found this when I restarted my docker-based install and it upgraded. Pushed back the tag to 0.10.4 until it's fixed!

[gowthamsubbu]

@chrishoffman @jefferai Is the fix available in 0.11.0 image ? Or will be it in 0.11.1 ? We are still getting "Error failed to validate policy templating: unbalanced templating characters" exception when posting base64 encoded ACL policy.

{"path":{"secret/":{"capabilities":["read"]}}}
{"path":{"secret/":{"capabilities":["read"]} } }

[chrishoffman]

There will be a 0.11.1 shortly to address this issue. You can also build from master right now to see if it addresses the issue.

[gowthamsubbu]

@chrishoffman Thanks for the update. I couldn't find the master tag in the Vault docker hub.

[alitheg]

@gowthamsubbu That's exactly my issue - using docker means we're reliant on a build being produced and pushed to Docker Hub. I'm content to know it's fixed and incoming. Thanks for the update @chrishoffman!

[chrishoffman]

I meant from source. We don't publish master docker images.

[alexwwang]

I have to use HCL format to compose my policy strings instead of json format to bypass this bug in vault 0.11.