Jiashuo Li
Jiashuo Li
Linux is a little bit different from Windows. As explained in https://github.com/AzureAD/microsoft-authentication-extensions-for-python/wiki/Encryption-on-Linux > Encryption on Linux is available by using libsecret to connect to secret service running on your Linux...
`https://aka.ms/InstallAzureCli` from https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-linux?pivots=script is for **interactive installation from PyPI**. Since you are using "Custom Script Extension", I think it doesn't have a TTY, so the error happens. I guess previously...
The equivalent of Azure CLI `az ad` command group is [`AzAD`](https://docs.microsoft.com/en-us/powershell/module/az.resources/?view=azps-7.3.2#active-directory) from Azure PowerShell. `AzureAD` on the other hand is a module developed by Azure Active Directory. `az ad` commands...
First of all, we use `equirements.py3.*.txt` files to guarantee built packages like `deb`, `rpm` are stable. That's why indirect dependencies are also included. > * `requirements.py3.windows.txt` is missing `wrapt` `wrapt`...
Ops. Looks like it has been reported before - https://github.com/kevin1024/vcrpy/issues/524.
Hi @DevilXD, I am facing a similar issue. However, I think for your demo script, calling `before_record_request` twice isn't the reason for the failure. `google.yaml` does have the correct filtered...
I saw MSAL's CI still has tests for Python 2.7, 3.5 and 3.6:  Azure CLI (https://github.com/Azure/azure-cli/issues/19858) and Azure Python SDK (https://github.com/Azure/azure-sdk-for-python/issues?q=is%3Aissue+is%3Aopen+drop+3.6) have now dropped Python 3.6. [Python 3.6 is...
Azure CLI never used `validate_authority` and everything works fine. Per our observation, all Azure Stack environments utilizing ADFS have the `/adfs` postfix in their authentication endpoint URL, which makes MSAL...
This issue also happens for https://github.com/Azure/azure-cli/issues/20507 where `ValueError` is raised for an invalid tenant. > Perhaps, you can get the best of both worlds, by implementing several smaller exception handlers....
I made a draft to demonstrate how it will look like if all MSAL interactions are wrapped with try-except clauses: https://github.com/Azure/azure-cli/pull/23311