Skip to content

azure-quantum authentication get_token failed messages #67

@vxfield

Description

@vxfield

When authenticating with azure-quantum and using the default DefaultAzureCredential, it will try several authentication mechanisms as described here.

Even if one of the authentication methods happen to succeed, you will see the messages for the authentication methods that didn't succeed before the final (successful) authentication method was attempted.

So you may see a message like this, even if the authentication succeeded.

EnvironmentCredential.get_token failed: EnvironmentCredential authentication unavailable. Environment variables are not fully configured.
ManagedIdentityCredential.get_token failed: ManagedIdentityCredential authentication unavailable, no managed identity endpoint found.
SharedTokenCacheCredential.get_token failed: SharedTokenCacheCredential authentication unavailable. No accounts were found in the cache.
VisualStudioCodeCredential.get_token failed: Failed to get Azure user details from Visual Studio Code.
AzureCliCredential.get_token failed: Please run 'az login' to set up an account

This is the current behavior of the Azure.Identity.DefaultAzureCredential and a corresponding issue was filled to the Azure SDK team.

Meanwhile, please ignore the get_token failed messages if the authentication succeeded (i.e. you were able to submit jobs to Azure Quantum, etc.).

If all authentication methods have failed, then you may pay close attention to all attempts that have failed and see what was missing to the method that you were interested in.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions