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 - No passing user identity #631

Closed
mikenorgate opened this issue Dec 14, 2017 · 3 comments
Closed

Azure Key Vault - No passing user identity #631

mikenorgate opened this issue Dec 14, 2017 · 3 comments
Assignees
Milestone

Comments

@mikenorgate
Copy link

mikenorgate commented Dec 14, 2017

I'm attempting to insert a secret into Key Vault but always get a 401 response. Looking at the Azure logs I can see that there is no identity being passed with the request

I am using Terraform version 0.10.6 and version 0.3 of the AzureRM provider

The terraform excerpt is

resource "azurerm_key_vault_secret" "my_secret" {
  name      = "my_secret"
  value     = "my_secret_value"
  vault_uri = "https://XXX.vault.azure.net/"
}

In the Azure diagnostics logs I can see the request and it doesn't show an identity

{
	 "category": "AuditEvent",
	 "operationName": "Authentication",
	 "resultType": "Success",
	 "identity": {},
	 "properties": {"clientInfo":"HashiCorp-Terraform-v0.10.6","httpStatusCode":401,"requestUri":"https://XXX.vault.azure.net/secrets/my_secret?api-version=2016-10-01"},
	 "operationVersion": "2016-10-01",
	 "resultSignature": "Unauthorized",
	 "durationMs": "60"
}
@digitaldelirium
Copy link

FWIW - I'm getting the same behavior on azurerm provider version 1.0 and Terraform version 0.11.1
Terraform v0.11.1

  • provider.azurerm v1.0.0
  • provider.random v1.1.0
    But I'd definitely recommend that you upgrade with terraform init -upgrade

@tombuildsstuff tombuildsstuff added this to the 1.1.2 milestone Feb 7, 2018
@tombuildsstuff tombuildsstuff self-assigned this Feb 15, 2018
@tombuildsstuff tombuildsstuff modified the milestones: 1.1.2, 1.1.3, Future Feb 15, 2018
@achandmsft achandmsft modified the milestones: Future, 1.4.0 Mar 10, 2018
@achandmsft achandmsft added M1 and removed M1-priority labels Mar 10, 2018
@tombuildsstuff
Copy link
Contributor

Closing this in favour of #656 since it's a duplicate

@tombuildsstuff tombuildsstuff modified the milestones: 1.4.0, 1.3.3 Apr 17, 2018
@ghost
Copy link

ghost commented Mar 31, 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 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!

@ghost ghost locked and limited conversation to collaborators Mar 31, 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

4 participants