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

Approle permission denied on version 4.0.0 #2197

Closed
sergeyrudenko111 opened this issue Mar 18, 2024 · 1 comment · Fixed by #2198
Closed

Approle permission denied on version 4.0.0 #2197

sergeyrudenko111 opened this issue Mar 18, 2024 · 1 comment · Fixed by #2198
Labels

Comments

@sergeyrudenko111
Copy link

Terraform Core Version

1.7.5

Terraform Vault Provider Version

4.0.0

Vault Server Version

1.15.6

Affected Resource(s)

vault_auth_backend

Expected Behavior

Being able to read from data source vault_auth_backend.

Actual Behavior

permission denied, works on 3.25.0

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

data "vault_policy_document" "approle_readwrite" {
  rule {
    path         = "sys/auth"
    capabilities = ["create", "read", "update", "delete", "list"]
  }

  rule {
    path         = "auth/approle/role/*"
    capabilities = ["create", "read", "update", "delete", "list"]
  }
}

Steps to Reproduce

change the policy path for Approle Auth method from sys/auth to sys/auth/approle doesn't work

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

@fairclothjm
Copy link
Contributor

@sergeyrudenko111 Thanks for reporting and I am sorry you are having trouble. For now you can update your capabilities to include sudo. This should prevent permission denied on vault_auth_backend.

We are working to remove the sudo requirement for auth paths in the upcoming release. However you will need to update your policy path to use sys/mounts/auth/*.

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