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

azuredns: CLI authentication doesn't respect tenant setting #2178

Closed
3 tasks done
orgads opened this issue May 6, 2024 · 0 comments · Fixed by #2176
Closed
3 tasks done

azuredns: CLI authentication doesn't respect tenant setting #2178

orgads opened this issue May 6, 2024 · 0 comments · Fixed by #2176

Comments

@orgads
Copy link
Contributor

orgads commented May 6, 2024

Welcome

  • Yes, I'm using a binary release within 2 latest releases.
  • Yes, I've searched similar issues on GitHub and didn't find any.
  • Yes, I've included all information below (version, config, etc).

What did you expect to see?

I'm using terraform acme provider. I set AZURE_AUTH_METHOD to cli, and AZURE_TENANT_ID to a tenant which is not my primary. I expect it to work and use the specified tenant.

What did you see instead?

The tenant is not respected, and authentication fails.

How do you use lego?

Library

Reproduction steps

resource "acme_certificate" "certificate" {
  # ...
  dns_challenge {
    provider = "azuredns"

    config = {
      AZURE_AUTH_METHOD     = "cli"
      AZURE_TENANT_ID       = "<my-non-primary-tenant>"
      AZURE_RESOURCE_GROUP  = "dns-rg"
      AZURE_ZONE_NAME       = local.root_domain
    }
}

Version of lego

v4.16.1

Logs

Go environment (if applicable)

$ go version && go env
# paste output here
@orgads orgads added the bug label May 6, 2024
orgads added a commit to orgads/lego that referenced this issue May 6, 2024
Users with several tenants should have a way to use a specific one for
authentication.

Fixes go-acme#2178.
@ldez ldez changed the title Azure CLI authentication doesn't respect tenant setting azuredns: CLI authentication doesn't respect tenant setting May 6, 2024
orgads added a commit to orgads/lego that referenced this issue May 6, 2024
Users with several tenants should have a way to use a specific one for
authentication.

Fixes go-acme#2178.
orgads added a commit to orgads/lego that referenced this issue May 6, 2024
Users with several tenants should have a way to use a specific one for
authentication.

Fixes go-acme#2178.
ldez pushed a commit to orgads/lego that referenced this issue May 7, 2024
Users with several tenants should have a way to use a specific one for
authentication.

Fixes go-acme#2178.
@ldez ldez closed this as completed in #2176 May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants