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 Microsoft.Azure.Management.*.Fluent packages depend on Microsoft.Rest.ClientRuntime.Azure.Authentication, which depends on Microsoft.IdentityModel.Clients.ActiveDirectory version 2.x under .Net Framework 4.5.2 but version 3.x under .Net Framework 4.6.1.
Since .Net Framework 4.5.2 is the very oldest framework not yet to be out of support, it seems a bit risky to target it. But the API change between Microsoft.IdentityModel.Clients.ActiveDirectory 2.x and 3.x breaks ARMClient quite badly: all of the methods it uses from AuthenticationContext are either renamed or removed.
Half of the problems are easily handled by shimming the missing AcquireToken methods with extension methods which call AcquireTokenAsync, but the other half are due to ADAL v3 not exposing refresh tokens. AIUI AcquireTokenSilentAsync is supposed to replace AcquireTokenByRefreshTokenAsync, but I don't understand ADAL well enough to be confident in writing a patch for this.
The text was updated successfully, but these errors were encountered:
The scenario is using ARMClient to acquire tokens for use with the current Azure management libraries and .Net framework. Strictly speaking it can be done without ADAL v3 by doing complicated hacks to load one version of Microsoft.IdentityModel.Clients.ActiveDirectory into one appdomain for token acquisition and another version into a different appdomain for the Azure management, but that's not exactly KISS.
Are there any plans to support ADAL v3?
The
Microsoft.Azure.Management.*.Fluent
packages depend onMicrosoft.Rest.ClientRuntime.Azure.Authentication
, which depends onMicrosoft.IdentityModel.Clients.ActiveDirectory
version 2.x under .Net Framework 4.5.2 but version 3.x under .Net Framework 4.6.1.Since .Net Framework 4.5.2 is the very oldest framework not yet to be out of support, it seems a bit risky to target it. But the API change between
Microsoft.IdentityModel.Clients.ActiveDirectory
2.x and 3.x breaksARMClient
quite badly: all of the methods it uses fromAuthenticationContext
are either renamed or removed.Half of the problems are easily handled by shimming the missing
AcquireToken
methods with extension methods which callAcquireTokenAsync
, but the other half are due to ADAL v3 not exposing refresh tokens. AIUIAcquireTokenSilentAsync
is supposed to replaceAcquireTokenByRefreshTokenAsync
, but I don't understand ADAL well enough to be confident in writing a patch for this.The text was updated successfully, but these errors were encountered: