Interactive login with `az login` is not working about kitchen-azurerm HOT 8 OPEN

Here is my (sanitized) .kitchen.yml config:

driver:
  name: azurerm
  subscription_id: SUBSCRIPTION_GUID
  transport:
    name: winrm
    winrm_transport: ssl
    
  instance_type: Standard_D2_v2
  location: "East US"
  vnet_id: VNET_URN
  subnet_id: VNET_SUBNET_URN

platforms:
  - name: windows2019
    driver:
      image_urn: MicrosoftWindowsServer:WindowsServer:2019-Datacenter-smalldisk:latest
      use_ephemeral_osdisk: true

suites:
  - name: msbase
    driver:
      vm_name: tk-server-2019-nilla

from kitchen-azurerm.

It's worthy to note that the Azure CLI is authenticated and I can run commands against this subscription from the command line when this issue occurs with the kitchen-azurerm driver.

from kitchen-azurerm.

I am encountering the same issue. @bender-the-greatest - did you ever find a workaround?

from kitchen-azurerm.

I have not, but it's not been a high priority to revisit yet. Note that I have not tried providing an explicit client id and secret, so an app registration (service principal) with the permissions necessary for kitchen-azurerm to function may be a suitable workaround.

from kitchen-azurerm.

@rogueautomation I did work around this, right now my workaround is to use an app registration and credentials file

from kitchen-azurerm.

@bender-the-greatest @rogueautomation any luck with this issue? i am facing the same problem.

from kitchen-azurerm.

@shyambandi - not as of yet. Our workaround is currently running WSL 2, installing az cli and CHEF Workstation in our Ubuntu WSL VM's and running test-kitchen that way. I'm told that more and more folks are bringing this issue up to CHEF, but haven't heard on a target date for their prospective fix.

from kitchen-azurerm.

@rogueautomation i am running this on a Windows machine, can you suggest?

from kitchen-azurerm.