You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After azure-keyvault-keys==4.5.0b5 was released, Azure CLI pinned azure-keyvault-keys to 4.5.0b4 as a quick fix (#20880).
Later on, tenant_id is discarded in get_token as another quick fix to support new azure-keyvault-keys (#21244).
Now, azure-storage-blob will also implement authentication challenge (#20969). Even though azure-storage-blob currently doesn't pass tenant_id to get_token, it is possible this will be implemented in the future.
Proposed solution
Azure CLI should support get_token(tenant_id=...) API like azure-identity, so that Azure CLI can get an access token for another tenant using the refresh token of the current tenant.
Additional context
This approach adds additional complexity in error handling. Without this feature, if tenants don't match, we can simply fail with
The tenant in the authentication challenge doesn't match the current tenant.
However, if this is supported, and refreshing fails due to reasons such as conditional access (MFA), we will show another error message like
Authentication failed because MFA is needed.
The text was updated successfully, but these errors were encountered:
ghost
added
the
needs-triage
This is a new issue that needs to be triaged to the appropriate team.
label
Feb 14, 2022
Context
azure-keyvault-keys==4.5.0b5
made a breaking change for authentication:It uses
azure-identity
's new multi-tenant authentication APIget_token(tenant_id=...)
fromAfter
azure-keyvault-keys==4.5.0b5
was released, Azure CLI pinnedazure-keyvault-keys
to4.5.0b4
as a quick fix (#20880).Later on,
tenant_id
is discarded inget_token
as another quick fix to support newazure-keyvault-keys
(#21244).Now,
azure-storage-blob
will also implement authentication challenge (#20969). Even thoughazure-storage-blob
currently doesn't passtenant_id
toget_token
, it is possible this will be implemented in the future.Proposed solution
Azure CLI should support
get_token(tenant_id=...)
API likeazure-identity
, so that Azure CLI can get an access token for another tenant using the refresh token of the current tenant.Additional context
This approach adds additional complexity in error handling. Without this feature, if tenants don't match, we can simply fail with
However, if this is supported, and refreshing fails due to reasons such as conditional access (MFA), we will show another error message like
The text was updated successfully, but these errors were encountered: