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
{{ message }}
This repository has been archived by the owner on Apr 10, 2024. It is now read-only.
This for example will fail in Container Apps, and it impacts Azure CLI commands like az login --identity
The correct implementation would be to check for the combination IDENTITY_ENDPOINT and IDENTITY_HEADER. You can also check for MSI_ENDPOINT and MSI_SECRET, but these are just aliases to support legacy app behavior. The IDENTITY_ENDPOINT and IDENTITY_HEADER is the proper way to determine if you should be using the App Service protocol or IMDS.
Hi @mattchenderson
This project is deprecated and no longer receives support. All recent (less than 2 years) SDKs now support azure-identity to provide MSI authentication with complete support from the team, to replace this library.
If you're stuck in a project that do requires msrestazure, please open an issue on azure-sdk-for-python to understand what we can do to help you move to azure-identity.
Thanks!
The following checks are not inline with the actual behavior of these services:
msrestazure-for-python/msrestazure/azure_active_directory.py
Lines 552 to 554 in 8849f39
msrestazure-for-python/msrestazure/azure_active_directory.py
Line 585 in 8849f39
This for example will fail in Container Apps, and it impacts Azure CLI commands like
az login --identity
The correct implementation would be to check for the combination IDENTITY_ENDPOINT and IDENTITY_HEADER. You can also check for MSI_ENDPOINT and MSI_SECRET, but these are just aliases to support legacy app behavior. The IDENTITY_ENDPOINT and IDENTITY_HEADER is the proper way to determine if you should be using the App Service protocol or IMDS.
Reference for the token service API can be found here: https://docs.microsoft.com/azure/app-service/overview-managed-identity#rest-endpoint-reference
The text was updated successfully, but these errors were encountered: