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
SSH extension should detect the CLI version or other field added in the future whether the underlying auth library is MSAL. If so, it should call Profile.get_login_credentials and call get_token on the returned credential instead of calling Profile.get_msal_token:
jiasli
changed the title
SSH extension should remove the usage of get_msal_token
[SSH] SSH extension should remove the usage of get_msal_token
Jan 22, 2021
Extension name (the extension in question)
SSH
Description of issue (in as much detail as possible)
In the old ADAL-based Azure CLI, no interface is provided to pass
data
to ADAL and AAD to get an SSH cert. None of these methods can do this:Profile.get_raw_token
AdalAuthentication.signed_session
AdalAuthentication.get_token
That's why
Profile.get_msal_token
is introduced (Azure/azure-cli#12999) to senddata
to MSAL and AAD.Now in the new beta MSAL-based Azure CLI,
Profile.get_login_credentials
returns aCredentialAdaptor
which is compatible with Track 2 SDK'sTokenCredential
.SSH extension should detect the CLI version or other field added in the future whether the underlying auth library is MSAL. If so, it should call
Profile.get_login_credentials
and callget_token
on the returned credential instead of callingProfile.get_msal_token
:azure-cli-extensions/src/ssh/azext_ssh/custom.py
Line 58 in ecaacbb
which will be deprecated in the GA release of MSAL-based Azure CLI.
The text was updated successfully, but these errors were encountered: