Login failed with the same credentials

[csaba-kovacs]

I'm facing an issue where the same AZ login step fails, but I'm using the same credentials in the secret.

Both step contains only the creds option:

Any idea where this comes from? Why does the creds fields look different?

[BALAGA-GAYATRI]

Hi, can you please share your workflow for more details? Also please tell us since when it is happening for you

[rituparnop]

Facing same issue. Suddenly creds stopped working last week without any changes. Similar to #205. Tried creating new creds but that failed too. This is second action in workflows just after checkout. Need an urgent fix for this as whole build is broken now.

[BALAGA-GAYATRI]

Can you please confirm if you are generating credentials using -

   az ad sp create-for-rbac --name "myApp" --role contributor \
                            --scopes /subscriptions/{subscription-id}/resourceGroups/{resource-group} \
                            --sdk-auth

as mentioned in the readme? Please make sure you are including --sdk-auth without which the action throws error.

[csaba-kovacs]

Can this be done from the portal? I don't have full admin privileges to recreate or add the --sdk-auth option to the currently available service principal. And i would still not understand how did it work before. The SP was created from the portal.

[rituparnop]

Working creds created using --sdk-auth option.
Anyway solved this by installing azure cli separately before azure/login step.

      - name: Install Azure cli
        run: |
          sudo apt-get install ca-certificates curl apt-transport-https lsb-release gnupg
          curl -sL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/microsoft.gpg > /dev/null
          AZ_REPO=$(lsb_release -cs)
          echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $AZ_REPO main" | sudo tee /etc/apt/sources.list.d/azure-cli.list
          sudo apt-get update
          sudo apt-get install azure-cli

[csaba-kovacs]

Working creds created using --sdk-auth option. Anyway solved this by installing azure cli separately before azure/login step.

      - name: Install Azure cli
        run: |
          sudo apt-get install ca-certificates curl apt-transport-https lsb-release gnupg
          curl -sL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/microsoft.gpg > /dev/null
          AZ_REPO=$(lsb_release -cs)
          echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $AZ_REPO main" | sudo tee /etc/apt/sources.list.d/azure-cli.list
          sudo apt-get update
          sudo apt-get install azure-cli

You added the --sdk-auth first then installed the CLI before the login step?

[BALAGA-GAYATRI]

@csaba-kovacs you might need to try OIDC login. Readme has more details on getting started with it.

[github-actions]

This issue is idle because it has been open for 14 days with no activity.

[MrCliff]

For us the same error seems to occur randomly on some workflow runs but then go away after retrying the run. This is really annoying, because we have multiple pipelines and some seem to be broken every day but after retries the problem goes away. We use the Azure PS session.

And actually it seems you have the exactly same problem in your pipelines which seems to go away after another run on the same version.