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
Reason being it is easier to use ChainedTokenCredential and force auth to resolve auth using only ManagedIdentityCredential and EnvironmentCredential for example. Without the use of ChainedTokenCredential, you have to use a whole bunch of exclude flags on DefaultAzureCredentialOptions (see example below). To me, this feels bit clunky.
There was a survey I filled recently on LinkedIn on this topic, and I thought I will log this as a discussion item today.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Can we please use a subclass of TokenCredential, rather than use DefaultAzureCredential always?
PowerPlatform-DataverseServiceClient/src/GeneralTools/DataverseClient/Extensions/Microsoft.PowerPlatform.Dataverse.Client.AzAuth/AzAuth.cs
Line 20 in e5c182b
Reason being it is easier to use ChainedTokenCredential and force auth to resolve auth using only ManagedIdentityCredential and EnvironmentCredential for example. Without the use of ChainedTokenCredential, you have to use a whole bunch of exclude flags on DefaultAzureCredentialOptions (see example below). To me, this feels bit clunky.
There was a survey I filled recently on LinkedIn on this topic, and I thought I will log this as a discussion item today.
Beta Was this translation helpful? Give feedback.
All reactions