Skip to content
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

sys/policies/acl/cf 403 on binding vault to app #51

Closed
rbprado opened this issue Jun 12, 2019 · 1 comment · Fixed by #68
Closed

sys/policies/acl/cf 403 on binding vault to app #51

rbprado opened this issue Jun 12, 2019 · 1 comment · Fixed by #68
Labels

Comments

@rbprado
Copy link

rbprado commented Jun 12, 2019

Hello I'm getting this 403 error on binding the app to the vault service:

$ cf bind-service my-app sbil-vault
Binding service sbil-vault to app my-app in org SvcsIT-AnEOrg / space devops as Rafael_Prado...
Service broker error: failed to create policy cf-eabb9d6c-2f3c-43ef-a76d-4e0e25eda128: Error making API request.
URL: PUT http://svcsltslab1.com/v1/sys/policies/acl/cf-eabb9d6c-2f3c-43ef-a76d-4e0e25eda128

Code: 403. Errors:
* 1 error occurred:
* permission denied
FAILED

I handled it by adding this to the cf-broker.hcl:

path "sys/policies/acl/cf-*" {
  capabilities = ["create", "update", "delete"]
}

This is not on the README.md doc, I was going to generate a PR for it but as I'm very new to vault and I don't know if it's correct to add this policy I believe that I should first ask about it here :)

@tvoran
Copy link
Member

tvoran commented Aug 12, 2022

Hi there, I think you're correct! And we should update the README. It looks like a while ago the vault client switched from using sys/policy to sys/policies/acl when creating and updating policies in Vault: hashicorp/vault#5583 So I think that's where the discrepancy came from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants