Managed Identity - failed network request returns wrong error type #7100
Labels
bug
A problem that needs to be fixed for the feature to function as intended.
confidential-client
Issues regarding ConfidentialClientApplications
msal-node
Related to msal-node package
Core Library
MSAL Node (@azure/msal-node)
Core Library Version
2.8.1
Wrapper Library
Not Applicable
Wrapper Library Version
None
Public or Confidential Client?
Confidential
Description
This issue has been raised by the Azure Identity SDK team while adopting msal-node's Managed Identity implementation.
On error, something like this is shown as the error message.
ServerError: bad request: undefined - [undefined]: undefined - Correlation ID: undefined - Trace ID: undefined
Question: Does the IMDS endpoint return the data needed to populate the error message
here?
Answer: a
managed_identity_request_failed
error should be thrown, showing the correlation id and any other details returned from the managed identity source.Error Message
No response
MSAL Logs
No response
Network Trace (Preferrably Fiddler)
MSAL Configuration
Relevant Code Snippets
Reproduction Steps
N/A
Expected Behavior
N/A
Identity Provider
Entra ID (formerly Azure AD) / MSA
Browsers Affected (Select all that apply)
None (Server), Other
Regression
No response
Source
Internal (Microsoft)
The text was updated successfully, but these errors were encountered: