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
The experience above shows 1 hop chaining, but there are scenarios where there could be several hops, i.e. "AzureAd" uses a credential from "AzureAdCredentialSource1" which in turn uses a credential from "AzureAdCredentialSource2", which in turn uses a certificate.
Audience
The audience (TokenExchangeUrl) is mandatory, to prevent app developers from using the api://AzureADTokenExchange/ in other clouds. This url is for the public cloud only.
The SDK shall take care of adding /.default when making the token request.
Implementation Details
Internally, this should reuse the TokenAcquisition classes that use MSAL.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Federated Identity Credentials can come from:
SignedAssertionFilePath
)SignedAssertionFromManagedIdentity
)Describe the solution you'd like
A new credential named
SignedAssertionFromIdentityProvider
that supports getting an assertion from Entra.Note: bottom turtle reference
Multiple credential chaining
The experience above shows 1 hop chaining, but there are scenarios where there could be several hops, i.e. "AzureAd" uses a credential from "AzureAdCredentialSource1" which in turn uses a credential from "AzureAdCredentialSource2", which in turn uses a certificate.
Audience
The audience (
TokenExchangeUrl
) is mandatory, to prevent app developers from using theapi://AzureADTokenExchange/
in other clouds. This url is for the public cloud only.The SDK shall take care of adding
/.default
when making the token request.Implementation Details
Internally, this should reuse the TokenAcquisition classes that use MSAL.
The text was updated successfully, but these errors were encountered: