Skip to content

2.83.0 Fails to cache logins for non-ARM resources #32853

@ld0614

Description

@ld0614

Describe the bug

When using 2.83.0, any commands that make use of alternative resources (not the default ARM resource) fail to retrieve their tokens from the MSAL Cache. This works correctly in 2.82.0 (rollback also fixes the issue) and equivalent commands work correctly in PowerShell (Az.Accounts 5.3.1) so the permissions are set up correctly in Azure/Entra ID

if you run 'az login' the command successfully authenticates, enumerates the subscriptions and allows for subscription related commands to work correctly

When running any non-ARM related extensions (such as accessing devops or the containerapp/serviceconnector-passwordless to set up managed service access to managed service identity) these commands fail in version 2.83.0 as they are unable to access the requires tokens from the MSAL cache

Related command

az account get-access-token --resource-type oss-rdbms
az devops project list

Errors

cli.azure.cli.core.azclierror: Can't find token from MSAL cache.
az_command_data_logger: Can't find token from MSAL cache.
To re-authenticate, please run:
az login

Issue script & Debug output

I can provide in-depth output if needed

Expected behavior

Access token should be returned/commands should work

Environment Summary

{
"azure-cli": "2.83.0",
"azure-cli-core": "2.83.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"containerapp": "1.3.0b3",
"serviceconnector-passwordless": "3.3.6",
"ssh": "2.0.6"
}
}

Additional context

No response

Metadata

Metadata

Assignees

Labels

ARMaz resource/group/lock/tag/deployment/policy/managementapp/account management-groupAccountaz login/accountAuto-AssignAuto assign by botAzure CLI TeamThe command of the issue is owned by Azure CLI teamBreaking ChangeDevOpsService AttentionThis issue is responsible by Azure service team.Similar-IssuebugThis issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions