Duplicate ManagedIdentitySourceName #7181
Labels
bug-unconfirmed
A reported bug that needs to be investigated and confirmed
confidential-client
Issues regarding ConfidentialClientApplications
msal-node
Related to msal-node package
question
Customer is asking for a clarification, use case or information.
Core Library
MSAL Node (@azure/msal-node)
Core Library Version
2.9.2
Wrapper Library
Not Applicable
Wrapper Library Version
None
Public or Confidential Client?
Confidential
Description
ManagedIdentitySourceNames defines both
Imds
andDefaultToImds
but only one of these is actually used in getManagedIdentitySourceWe should remove one of the two, probably
Imds
, from the public APIAlternatively, you could update the
getManagedIdentitySource
s type to:So developers writing code against this know which value to check against when they want to do something special for IMDS flows (like probing the IMDS endpoint) instead of always remembering to check both values (or looking into the implementation to see that only one is actually used)
playground example
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)
Regression
No response
Source
Internal (Microsoft)
The text was updated successfully, but these errors were encountered: