-
Notifications
You must be signed in to change notification settings - Fork 155
[Feature Request] Make managed identity token parse failures distinct #907
Copy link
Copy link
Closed
Labels
AzureSDKIssues and requests affecting the Azure SDKIssues and requests affecting the Azure SDKBugSomething isn't working, needs an investigation and a fixSomething isn't working, needs an investigation and a fixP2Normal priority items, should be done after P1Normal priority items, should be done after P1confidential-clientFor issues related to confidential client appsFor issues related to confidential client apps
Description
MSAL client type
Managed identity
Problem Statement
In Azure Identity before we switched to using MI from MSAL, we were able to throw a distinct exception in the case of an invalid json response from the IMDS endpoint. This let us detect cases such as a proxy.
Proposed solution
We need ManagedIdentityApplication to notify us that the response was malformed json. .NET did this work here: AzureAD/microsoft-authentication-library-for-dotnet#5038 - we need roughly the same thing.
Alternatives
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
AzureSDKIssues and requests affecting the Azure SDKIssues and requests affecting the Azure SDKBugSomething isn't working, needs an investigation and a fixSomething isn't working, needs an investigation and a fixP2Normal priority items, should be done after P1Normal priority items, should be done after P1confidential-clientFor issues related to confidential client appsFor issues related to confidential client apps