-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API call "read entities by name" failes for entities with spaces #7054
Comments
jefferai
added a commit
that referenced
this issue
Jul 3, 2019
We don't restrict the name itself, so we shouldn't restrict lookup. Fixes #7054
jefferai
added a commit
that referenced
this issue
Jul 3, 2019
We don't restrict the name itself, so we shouldn't restrict lookup. Fixes #7054
jefferai
added a commit
that referenced
this issue
Jul 3, 2019
We don't restrict the name itself, so we shouldn't restrict lookup. Fixes #7054
Fixed, thanks! |
Wow that was fast, thank you! :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using the read entities by name api call for an entity that has as space in the name I get a 404 with he following payload
{"errors":["1 error occurred:\\n\\t* unsupported path\\n\\n"]}\n
To Reproduce
Steps to reproduce the behavior:
curl \ --header "X-Vault-Token: ..." \ http://127.0.0.1:8200/v1/identity/entity/name/testentity%20name
Expected behavior
API call should return the entity
Environment:
Vault Server Version (retrieve with
vault status
): 1.1.2Vault CLI Version (retrieve with
vault version
): Vault v1.1.2 ('0082501623c0b704b87b1fbc84c2d725994bac54')Server Operating System/Architecture: Docker on Linux
The text was updated successfully, but these errors were encountered: