-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
azurerm_key_vault_certificate 401 when trying to create a new self-signed certificate #1584
Comments
hey @Supermathie Thanks for opening this issue :) Taking a look into this - would it be possible to confirm how you're authenticating to Azure with Terraform, either using the Azure CLI/MSI or a Service Principal? There's a known issue with Azure CLI authentication and KeyVaults (which is fixed in the next release) where a 401 is returned, which looks to be the case in this instance. Thanks! |
@tombuildsstuff thanks - yes I'm authenticating via CLI So this will be fixed in 1.10? Fantastic! |
Yep - this was fixed in #1544 which has been merged and will be part of v1.10. Given this is a duplicate of Thanks! |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Community Note
Terraform Version
Terraform v0.11.7
Affected Resource(s)
Terraform Configuration Files
Debug Output
(available on request)
Panic Output
Expected Behavior
The certificate should have been created and issued
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
I know that my user does have permissions to the Key Vault as I can perform the operations via the CLI or Azure Portal.
References
The text was updated successfully, but these errors were encountered: