-
Notifications
You must be signed in to change notification settings - Fork 557
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
Feature request: Control which policies are to be used in the created child token at the provider level #1042
Comments
The policies I want to remove come from identity_policies, so it's not doable when creating a child token, cf https://discuss.hashicorp.com/t/create-token-issues-child-policies-must-be-subset-of-parent/5913/2 => the feature request would not help my scenario, closing it. |
Hello @thomas-riccardi
|
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
Affected Resource(s)
The vault provider itself.
Terraform Configuration Files
Expected Behavior
Specifying the token policies on the created child token works.
Actual Behavior
Specifying the token policies on the created child token is not supported: the created token automatically inherits all parent token policies.
This happens there:
terraform-provider-vault/vault/provider.go
Lines 810 to 815 in cffbae1
Context/need
I was hit by hashicorp/vault#3892 : adding more policies (via a OIDC group claims giving identity policies) (without any
deny
) unexpectedely removed permissions on some endpoints.One way to work around that would be to limit the policies used by the terraform-provider-vault when it creates a dedicated child token, thus regaining full access to proceed.
Maybe
orphan
would also be needed to disable the policies coming from the identity, but that may create other issues...The text was updated successfully, but these errors were encountered: