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

Azure Key Vault Secret / Issue With Access Policies #16908

Closed
hmarcelodn opened this issue Dec 13, 2017 · 2 comments
Closed

Azure Key Vault Secret / Issue With Access Policies #16908

hmarcelodn opened this issue Dec 13, 2017 · 2 comments

Comments

@hmarcelodn
Copy link

Hi Terraform Team,

I am working on provisioning a couple of Azure Key Vaults and its secrets.

I created the resources and assigned a few Access Policies:

1- My self full permissions
2- My terraform AD Application w/ full permissions
3- An application with get permissions

My user Access policy works just fine. But the other two policies appeared in the list but its like its not taking the avatar image, like it were not referencing to the real object in AD. As a result of that when I want to create secrets usings my Terraform AD Application it gave me "Access Denied".

I added manually the policy in the Key Vault and referenced the Terraform AD Application and I gave it the same full permissions then it worked. This time I see the same object_id referenced twice in the Access Policies list, the one I created manually works and the one with Terraform did not.

Any suggestion?

@hashibot
Copy link
Contributor

This issue has been automatically migrated to hashicorp/terraform-provider-azurerm#627 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.

@ghost
Copy link

ghost commented Apr 5, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants