- A user assigned managed identity can now be specified using its object ID. 4215.
WithTenantIdnow works with CIAM authorities. See 4191.- Improved the error message when cache serialization fails. See 4206.
- Improved logging when using the Windows broker (WAM). See 4183.
- The client-side telemetry API (
ITelemetryClient) is now generally available. See 3784. - Added
WithSearchInCacheForLongRunningProcess()modifier which allowsInitiateLongRunningProcessInWebApimethod to search in cache. This flag is intended only for rare legacy cases; for most cases, rely on the default behavior ofInitiateLongRunningProcessInWebApiandAcquireTokenInLongRunningProcess. See 4124.
WithTenantIdcan now be used with dSTS authorities to overwrite the tenant. See 4144, 4145.- Fixed a bug in token serialization for rare cases when an ID token has no
oidclaim. See 4140.
- Acquiring tokens with managed identity is now generally available. See 4125 and documentation for managed identity in MSAL.NET.
- Updated the managed identity API to specify the identity type when creating an
ManagedIdentityApplication. See 4114. - When acquiring tokens with managed identity and using the default HTTP client, MSAL will retry the request for certain exception codes. See 4067.
- Adds
MsalManagedIdentityExceptionclass that represents any managed identity related exceptions. It includes general exception information including the Azure source from which the exception originates. See 4041. - MSAL will now proactively refresh tokens acquired with managed identity. See 4062.
- MSAL will now proactively refresh tokens acquired using
AppTokenProviderAPI. See 4074. MsalExceptionand derived exception classes now have a propertyAdditionalExceptionData, which holds any extra error information. Currently it is only populated for exceptions coming from the Windows authentication broker (WAM). See 4106.- For HTTP telemetry. added a new telemetry ID for long-running on-behalf-of requests. See 4099.
- Fixed a JSON serialization issue in iOS apps that are built in release Ahead-Of-Time (AOT) compilation mode. See 4082.
- MSAL.NET package now references correct Microsoft.iOS version. See 4091.
- Microsoft.Identity.Client.Broker package can now be used in projects which rely on the older package.config. See 4108.
- Fixed a
user_mismatcherror whenWithAccountis specified when acquiring tokens interactively and selecting a different account in the account picker. See 3991.
- Added support for CIAM authorities. See 3990.
- Fixed issue where WAM is invoked for B2C authorities. MSAL will now fall back to the browser for this scenario. See 4072.
- The improved experience using Windows broker (WAM) is now generally available for all desktop platforms, except UWP. See 3375, 3447.
- Acquiring Proof-of-Possession tokens on public desktop clients using WAM broker is now generally available. See 3992.
- The requirement for a specific Windows SDK version on .NET 6 platform has been removed, which should improve the package usage on .NET 6 platforms. MSAL.NET now targets a more general
net6.0-windowsinstead ofnet6.0-windows10.0.17763.0. See 3986. - Added support for non-Azure AD IdP's in client credential flows. Use
WithGenericAuthority(authority). This is still an experimental API and may change in the future. See 4047, 1538. - Added
AuthenticationResult.AdditionalResponseParametersproperty bag with any extra parameters from the AAD response. This collection will also havespa_accountIdparameter which can be used in brokered hybrid single-page application (SPA) scenarios. See 3994.
- Simplified managed identity API. Use
ManagedIdentityApplicationBuilderto create aIManagedIdentityApplicationand callAcquireTokenForManagedIdentity. See 3970 and wiki. - Added
StopLongRunningProcessInWebApiAsyncwhich allows to remove cached tokens based on a long-running OBO key. See 3346 and wiki.
InitiateLongRunningProcessInWebApiwill now always acquire new tokens from AAD without checking the token cache first. See 3825.- When using preview Windows broker, MSAL will correctly handle the transitive reference to Microsoft.Identity.Client.NativeInterop. Any explicit references to Microsoft.Identity.Client.NativeInterop in projects also referencing MSAL should be removed. See 3964.
- Fixed preview Windows broker throwing a signed out exception when calling
AcquireTokenSilentafter acquiring token using the Username/Password flow. See 3916 and See 3961.
- Extended managed identity experimental functionality with support for Azure Cloud Shell. See 3832.
- Added support for PII logging for WAM preview. See 3845, 3822.
- Fixed JSON serialization issues for apps running on .NET 7. See 3892.
- Improved logging performance to only create logs when a specified log level is enabled. See 3901.
- Fixed
Unable to load DLL 'msalruntime'exception for apps that use WAM preview and are packaged as MSIX. See 3740. - WAM preview now honors the login hint. See 3301 and WAM docs.
- WAM preview now allows to sign in with an account different from the provided login hint. See 3929.
- Fixed an
ApiContractViolationexception in WAM preview when signing out. See 3685. - MSAL now allows passing no scopes when using WAM preview. See 3675.
- When broker is enabled, MSAL will now use the refresh token from the broker instead of a locally cached one. See 3613.
- Added a more descriptive error message when combined flat user and app cache is used. Use a partitioned token cache (for ex. distributed cache like Redis) or separate files for app and user token caches. See 3218.
- Updated logs to clarify that managed identity correlation ID differs from MSAL one. See #3908.
- Fixed an occasional cryptographic exception by removing the RSA public key size check - AAD is better suited to handle this verification. See 3896.
- Fixed JSON parsing errors when receiving an error token response. See 3883.
- Added better error handling when receiving WS-Trust responses. See 3614.
WithAuthoritymethods on the request builders are hidden. Use eitherWithTenantIdon the request builders orWithAuthorityonly on the application builder. See #2929.- Deprecated
IsBrokerAvailablemethod on mobile platforms. Applications should rely on the library automatically falling back to a browser if the broker is not available. See 3320. - Deprecated unused extended expiry API. See 1377.
- Extended managed identity experimental functionality with support for Azure Arc. See 3862
- Updated the Broker package to use Microsoft.Identity.Client.NativeInterop 0.13.3 to resolve crash related to garbage collection when using new WAM broker preview. See 3868
- Disabled additional logging in new WAM broker introduced in MSAL 4.49.0. See 3875
- MSAL will now use
<region>.login.microsoft.comwhen using regional ESTS-R for public cloud. See 3252 - Added support for acquiring Work and School accounts when calling
GetAccountsusing the new Broker preview. See 3458 - Added the ability to disable Instance Discovery/Authority validation using
WithInstanceDiscovery(bool enableInstanceDiscovery). See 3775 - Added new APIs to acquire authentication data from WWW-Authenticate and Authentication-Info request headers. This will provide additional support for Proof-of-Possession. See 3026
- Managed identities for Azure resources provide Azure services with an automatically managed identity in Azure Active Directory. You can use this identity to authenticate to any service that supports Azure AD authentication, without having credentials in your code. MSAL now supports acquiring token for managed identities for Azure App Services and Azure Virtual Machines. Use
WithManagedIdentity()method on theAcquireTokenForClientAPI to get an MSI token. This is an experimental feature and may change in the future versions of MSAL. See 3754 and 3829
- Enabled more logging for new WAM broker. See 3575
- Optimized MSAL cache key logic to improve performance. See 3393
- Fixes an internal (Microsoft 1P only) MSA-PT issue for the new WAM preview broker. See VS#1809364 and VS#1643652
- Added header title to the Account Picker for the new WAM preview broker. See 3803.
- Removed support for deprecated
net5.0-windows10.0.17763.0target. See 3770 and note below. - Added support for
net6.0andnet6.0-windows10.0.17763.0targets. See 3682 and note below. - Removed support for old
xamarinmac20target. See 3722. WithProofOfPossessionfor public client applications is now generally available. See 3767.- Added telemetry to log Proof-of-Possession usage. See 3718.
- Exposed tenant profiles for all authorities which are tenanted (B2C and dSTS). See 3703.
- Now logging MSAL version to common telemetry client. See 3745.
- Updated guidance on retry policies. See Retry Policy wiki and 3561.
- Fixed a
NullReferenceExceptionrelated to authority URLs when callingAcquireTokenSilentwith an Operating System account in apps using WAM. See 3769. - Fixed a
NullReferenceExceptionwhen using preview broker and callingAcquireTokenSilentwith MSA account and MSA-PT enabled. See 3743. - Added an
Exportedattribute to Android activities to be compliant with Android OS 12.1 (API 32) and above requirements. See 3680. - Fixed incorrect home account details in
AuthenticationResultofAcquireTokenByRefreshToken. See 3736.
If you have a Windows application which targets net5.0, net5.0-windows, net5.0-windowsX, net6.0, or net6.0-windows and would like to use either WAM or embedded browser, you must change the app target to at least net6.0-windows10.0.17763.0. System browser works on all of the above targets.
The recommendation is to use new Windows broker preview, as it offers better experience than current WAM implementation and will be generally available in the near future. If you want to try the new broker preview, install the NuGet package Microsoft.Identity.Client.Broker and call the .WithBrokerPreview() method. For details, see https://aka.ms/msal-net-wam.
- Hide legacy API's that are available only to internal Microsoft only (1P) applications. See 3670.
- Soft deprecate
WithAuthorityAPI on AcquireTokenXXX methods. Instead useWithTenantIdorWithTenantIdFromAuthority, orWithB2CAuthorityfor B2C authorities. See #3716 - Logging error codes to MSAL Telemetry. See 3595
- Add more logging around client creds and claims. See 3707.
- Improve extensibility APIs to support new POP
- Improved error messages when new preview broker exceptions are thrown. #3696
- MSAL will now throw an exception if no scopes are passed for the new preview Broker or for B2C scenarios. See #3675
- Removed .NET 6 MacCatalyst target because MSAL.NET doesn't currently support it. See #3693
- Throw an exception when new WAM DLLs are not loaded when invoking the new WAM preview broker. See #3699
- Fixes an internal (Microsoft 1P only) NuGet feed issue. See #3689
- Support for .NET MAUI is now generally available for iOS, Windows and Android targets. The package also works with UWP. Refer to
MauiStatus.mdfor details. - The new MSAL logging feature is now generally available.
WithExperimentalFeatures()is no longer required when callingWithLogging(). See 3548, wiki. - Adding IsProofOfPosessionSupportedByClient api to be used to determine if the current broker is able to support Proof-of-Posession. See 3496
- Adding ability to turn off the default retry-once policy on 5xx errors. See 2877
- Adds new public builder API accepting instances of
ITelemetryClient. See 3533. - Added logic to log some acquire token data via the new telemetry pipeline. See 3534.
- MSAL will now throw an exception if no scopes are passed when the new preview broker is invoked. See #3654 and #3677
MsalServiceException.IsRetryableis now correctly set. See #3661- Added extra logging in Preview Broker
RemoveAccountAsyncAPI. See #3658 - Added a check for null account in Preview Broker
RemoveAccountAsyncAPI. See #3657 AuthenticationResultnow shows correct authority for multi-cloud requests using WAM. See #3637- Adding null IdentityLogger to prevent null reference exception when using cache logger. See #3678
- WAM Authentication Library now explicitly supports .NET 4.6.2. See #3539
- Fixed 'Authenticator Factory has already been started` exception in new MSAL WAM preview. See #3604
- Added back missing .NET Standard 2.0 target to MSAL.NativeInterop package. See #3612
- [Resilience] Changed to an improved implementation of HTTP client factory on .NET Framework to improve resiliency (for ex. by reducing the amount of request timeouts). See #3546
- Logging additional exceptions to telemetry. See #3547
- Added Explicit .net 461 support to new WAM Preview broker. See 3550.
- Added MSALRuntime TelemetryData to verbose logging when a broker exception is thrown. See 3585
- Minor clarifications in caching logs. See 3582
- Added
AcquireTokenByUsernamePasswordflow in WAM broker preview. See 3308. - Added support for Proof-of-Possession tokens to
AcquireTokenByUsernamePasswordflow in WAM broker preview. See 3308. - Added
WithTenantIdFromAuthorityAPI to request builder. See 3429. - Exposed new Identity Logger in the
TokenCacheNotificationArgs. See 3404. - [Security] Increased size of PKCE verifier. See 1777.
- Enabled multi-cloud support in WAM. See 3477.
- Deprecated and replaced
SecureStringusage with strings. See 2437. - Refactored authority related code to use URI class instead of strings. See 3487.
- Fixed authority resolution for B2C authorities. See 3471.
- Improved WAM broker preview behavior for remembered accounts. See 3437.
- Obsoleted with a warning
AcquireTokenSilent(scopes, login_hint)for confidential client applications as it's not applicable in those scenarios. See 3403. - Now passing
intune_mam_resourceto the mobile broker. See 3490. - Fixed DSTS endpoints. See 3492.
- Cancellation tokens are now correctly passed to Windows broker and embedded web views. See 3225.
- Move app token provider feature to extensibility namespace and clarified its use. See 3475.
- Improved and simplified .NET Standard platform specific code. See 3451.
- Fix line endings in unit test files to enable running on Linux. See 3425.
This preview package adds support for.NET MAUI. It adds .NET 6 iOS and Android targets. The package also works with UWP. Refer to MauiStatus.md for details.
Upgrade the minimum target platform to 10.0.17763.0 Upgrade Microsoft.NETCore.UniversalWindowsPlatform to 6.1.9 or above Add a reference to Microsoft.IdentityModel.Abstractions, for projects that use package.json
Logs are now consistent when you use several .NET authentication libraries from Microsoft**. See 3028.
Exposed tenant ID and scopes in TokenCacheNotificationArgs. See 3389.
Added new WithClientAssertion API that exposes the token endpoint. See 3352.
Added additional descriptive information to error logs. See 3278.
Updated support from .NET Standard 1.3 to.NET Standard 2.0. See 1991.
Tenant profiles are now returned when calling GetAccounts with broker enabled. See 3349.
Fixed parsing of authentication result from broker preview. See 3354.
Fixed DSTS endpoints. See 3367.
Privacy and Terms of Use links are now visible in embedded picker UI on smaller screens. See 3153.
Fixed broker Proof-of-Possession token appearing as Bearer when calling GetAuthorizationHeader(). See 3353.
Ensured MSAL doesn't check local cache for tokens when using Proof-of-Possession with the broker preview. See 3363.
Added support in MSAL for dSTS authority See 3198.
Enabled Azure.Identity (Azure SDK) to benefit from MSAL.NET token cache when used for Managed Identity See 3137.
MSAL.NET now has a new WAM preview which is an abstraction layer based on MSAL C++ with support for Proof-of-Possession access tokens. This fixes some issues with current WAM implementation. See 3192 and wiki.
[IMPORTANT][RELIABILITY] In case of cancellation or timeout via CancellationToken, MSAL now throws the correct TaskCancelledException instead of MsalServiceException with error code request_tiomeout See 3283.
Fixed AcquireTokenSilent to not display a login prompt unnecessarily for operating system accounts in WAM. See 3294.
Fixed NullReferenceException in IsBrokerAvailable() See 3261.
Fixed a race condition to improve stability of region autodiscovery. See 3277.
Fixed a bug in instance discovery by adding pre-production environment (PPE) domains to known endpoints. See 3265.
Improved automated performance microbenchmarks to better reflect common scenarios See 3297 and wiki.
MSAL will now allow the use of different scopes when acquiring access tokens using a cached refresh token in long running On-Behalf-Of processes. See 2817.
MSAL now uses WebView1 instead of WebView2 for AcquireTokenInteractive with AAD or ADFS authority because WebView2 doesn't support SSO. See 3270.
Added Intune Mobile App Management (MAM) support for Android. See 3185.
MSAL.NET Cache Extensions now protects plaintext cache files with owner only read/write permissions.See 3186, 169.
Client capabilities flags are correctly passed to Android Broker. See 3203.
Fixed WithAccount(result.Account) to work when using WAM. See 3121.
Improved token cache filtering logic. See 3178, and 3233.
Fixed an error in creating UWP package for Microsoft Store upload. See 3184, 3239.
Fixed a bug to correctly sign-out an account from WAM. See 3248.
Correctly showing a browser in WSL2. See 3251.
Fixed a bug affecting WAM authentication with new accounts when the authority ends in /organizations. See 3217.
Fixed an error in creating UWP package for Microsoft Store upload. See 3184.
Multi Cloud Support Allows 1st party public client apps which target the public cloud to log in users from other clouds. Not supported for broker flows. See Multi-cloud support, 2524.
Expose the region or error used by MSAL in AuthenticationResult.AuthenticationResultMedatadata and in logs. See 2975.
App protection (true MAM) support for iOS. See 2894.
Fix a bug causing an "Sequence Contains No Elements" exception This occurs in rare circumstances when saving the token cache. 3130.
Fix a bug causing an "ArgumentOutOfRangeException: the relative expiration value must be positive" exception This occurs in rare circumstances when saving the token cache. 2859.
Default OS account login with MSA fails This affects some first party applications (MSA passthrough) when using WAM 3157.
WwwAuthenticateParameters should not expose Resource 3144.
MSAL now uses the WAM AAD plugin's account selector if authority is AAD only. This overcomes the issue of console apps not being able to display the account picker and other issues with Account Picker instability. See 2289.
Added OnBeforeTokenRequest public API which allows to execute a custom delegate before MSAL makes a token request. and enables support for legacy Proof-of-Possession implementations. See 3114.
Added kid in cache keys for client credential flows using Proof-of-Possession. See 3115.
Improved the error message when both region and custom metadata are configured. See 3014.
Exposed the ability to add a custom header text to auth dialogs such as WAM. See 3125.
MSAL now supports using Linux broker via Microsoft Edge. Use WithBroker() to authenticate with Microsoft Edge system browser, if installed, which integrates with Linux broker to offer a better authentication experience. See 3051.
Added support for WAM on Windows Server 2022 and Windows 11, and improved operation system detection for future versions. See 3040.
WAM is not supported on Windows Server 2016. MSAL will now fall back to browser if this OS is detected. See 2946.
Fix for GetAccountAsync API by checking for null on accountId parameter. See 3118.
WAM is not supported in pure ADFS environments. MSAL will now fall back to browser if the ADFS authority is used. See 2836.
Authorization Code for Single Page Applications (SPA) feature is now generally available. WithExperimentalFeatures() is no longer required when calling WithSpaAuthorizationCode(). See 2920, wiki, and sample.
Allow POP token envelope to be created externally. See 3059.
Remove obsolete telemetry (MATS) code to improve performance and stability. See 3043.
Log clarification in several places. See here and
here.
Allow res:// error pages to be displayed in embedded WebView. See 3083.
MSAL Logs are now more clear when regional is enabled and tokens are acquired from the cache. See 3073.
Added new LogLevel.Always and logging of important health metrics to help with diagnostics of MSAL. See 3004 and MSAL logging.
Fixed a crash in telemetry API when AcquireToken* builder is reused`. See 3024.
Fixed sending an incorrect backup authentication system (CCS) value in B2C apps. See 2748.
Disabling cache synchronization for confidential client apps by default to improve performance. See 2848.
MSAL now provides the correlation ID used in a to call Azure AD as part of cache callback (TokenCacheNotificationArgs). See 3008.
MSAL now provides a new specific API for long running web APIs, in addition to AcquireTokenOnBehalfOf, which no longer requests refresh tokens. The advantage is that the On-Behalf-Of token cache is now smaller and automatically has an eviction, and long running web APIs are easier to write. See https://aka.ms/msal-net-long-running-obo and 2733.
Added hybrid SPA support to MSAL. See https://aka.ms/msal-net/spa-auth-code and 2920.
Fixed issue where the authentication browser pop up would fail to show without an exception being thrown. See 2839.
MSAL WAM now properly signs out guest accounts. See 3016.
Reworded in-memory cache warning for web apps not using serialization. See 2990.
Fixed issue where Proof-of-Possession token does not rotate properly for confidential client applications. See 3003.
MSAL now returns a more descriptive exception when the browser back button is pressed during authentication. See 2991.
On the request builder, WithAuthority has been deprecated and WithTenantId was added as an alternative instead. See 2837.
MSAL will now only perform regional look up for client credential flows See 3029.
MSAL.NET now logs an error when common or organizations authority is used in AcquireTokenForClient. See #2887.
Added the ability to enable sending the certificate (as x5c) once when building the confidential client application, rather than on every single token acquisition request. See #2804.
Added additional methods to help create WwwAuthenticateParameters and get tenant ID by calling GetTenantId. See #2907, #2922.
Added an additional async overload for ConfidentialClientApplicationBuilder.CreateClientAssertion. See #2863.
Added an ability to enable a shared token cache between different MSAL client application instances, which can be set with the new WithCacheOptions API call. See Enabling shared cache, #2849.
Added an AuthenticationResult.AuthenticationResultMetadata.TokenEndpoint property from which you can derive which authority was effectively used to fetch the token. This can be used to determine if regional endpoint was used. See #2830.
Added a cache refresh reason and time remaining before proactive token refresh to AuthenticationResult.AuthenticationResultMetadata. See #2832.
Added the ability to specify tenant ID instead of the full authority at the token acquisition APIs level with WithTenantId. See #2280.
Improved support for calling regional endpoints, especially in Azure Functions. See #2803.
**Fixed a NullReferenceException when callingAcquireTokenInteractive with a login hint when using .WithBroker on Windows (WAM) **. See #2903.
Improved the error message when the application is throttled by the identity provider. See #2855.
When proactive token refresh is enabled, MSAL.NET now refreshes the tokens on a background thread to improve performance. See #2795.
Improved caching performance by adding partitioning to the default in-memory user cache used in user flows (like acquire token on-behalf-of, by authorization code). See #2861, #2881.
Improved performance by refactoring date handling when working with access tokens. See #2893.
Fixed a Non-HTTPS URL redirect is not supported in webview exception on Xamarin iOS for Facebook logins. See #2735.
Enabled setting the window title in WebView1 desktop browser. See #2936.
Added WithPrompt to the GetAuthorizationRequestUrl builder to give the ability to specify the interaction experience for the user. See #2896.
Added a more descriptive error message when WithAuthority is set at the request level and WithAzureRegion is used. See #2965.
MSAL.NET now logs an error when common or organizations authority is used in the client credentials request. See #2887.
Added the ability to enable sending the certificate (as x5c) once when building the confidential client application, rather than on every single request. See #2804.
Added additional methods to help create WwwAuthenticateParameters. See #2907.
Added an additional async overload for ConfidentialClientApplicationBuilder.CreateClientAssertion. See #2863.
Added an ability to enable a shared token cache between different MSAL client application instances, which can be set with the new WithCacheOptions API call. See Enabling shared cache, #2849.
Improved support for calling regional endpoints, especially in Azure Functions. See #2803.
Fixed a NullReferenceException when callingAcquireTokenInteractive with a login hint in WAM. See #2903.
Improved the error message when the application is throttled by the identity provider. See #2855.
When proactive token refresh is enabled, MSAL.NET now refreshes the tokens on a background thread to improve performance. See #2795.
Improved caching performance by adding partitioning to the default in-memory user cache used in user flows (like acquire token on-behalf-of, by authorization code). See #2861, #2881.
Improved performance by refactoring date handling when working with access tokens. See #2893.
Fixed a regression in authentication with the iOS broker. See #2913.
Added support for Application ID URIs to be used in confidential client applications. Confidential client applications, specifically web APIs, will now be able to use either the Client ID (GUID) or the Application ID URI, in the confidential client application builder. See #2852.
Added custom nonce support to Proof-of-Possession requests. See issue #2809.
Added a random jitter (within ten minutes range) to the Refresh In time for a token to optimize for resiliency. See issue #2796.
Added a more descriptive and actionable error message when AAD throttles the requests from the app. See issue #2808.
Improved error messaging related to broker support. See issue #2706.
MSA Pass-through enabled applications using MSAL can now use WAM. See issue #2822.
Improved error messaging when MSAL fails during the user realm discovery. See issue #2835.
Improved performance by removing unnecessary serialization in default app token cache used in client credentials flow. See issue #2826.
Fixed a race condition in confidential client requests when an authority with a different tenant is specified for each request. See issue #2798.
Fix to correctly propagate EnableCacheSynchronization flag from ConfidentialClientApplicationOptions. See pull request #2801.
AcquireTokenByIntegratedWindowsAuth provides better error messages. Error messages are now more actionable. See issue #2752
MSAL no longer performs instance discovery on well known authorities. This will improve performance for customers in regional scenarios See issue #2777
MSAL uses preferred_network name on sovereign clouds. Skipping discovery will improve the performance. See issue #2778
Error messages in Integrated Windows Authentication are now clearer. The following message related issues are fixed - #2731 - #2752
ConfidentialClientApplicationBuilder with auto region discovery no longer throws UriFormatException. This has been fixed by validating region string. See issue #2772
Memory leak in AuthorityEndpoint caching has been fixed. This will reduce memory leaks in the apps. See issue #2770
ADFS now has consistent values for UserName between STS and cache.. Tenant profiles will provide the consistency. #1559
MSAL.NET no longer throws ArgumentNullException when the parameters for WithCcsRoutingHint() are null. Authentication will now proceed as if not hint was provided. See issue #2755
MSAL no longer throws exceptions for mismatched authorities if they are known aliases. MSAL now ensures authorities configured in the application and request are not aliased before throwing. See issue #2736
WebView2 was throwing error when KeyDown was handled. This error has been removed. See issue #2685
Instance discovery was performed multiple times on non-public non-sovereign clouds. MSAL provides improved performance as it now only performs discovery when needed. See issue #2701
RemoveAsync(account) in confidential client apps now returns suggested web cache key. Empty key is no longer returned. #2643
Invalid syntax in XML comments for NoPromptFailedError and NoTokensFoundError has now been fixed. See issue #2756
MSAL.NET now enables confidential client apps to disable the internal cache semaphore by setting the EnableCacheSynchronization property to 'false'. This allows requests to bypass other requests that timeout, for example in the case of using a distributed cache. See PR #2702 for details.
Limits on URL length in embedded browsers was causing errors with auth code. Applications will not fail on the embedded browers due to the limitation. See issue #2743
IAccount now provides Tenant profile for each ID token. This will enable customers to get ID tokens in the authentication results. See issue #2583
MSAL now has WithCcsRoutingHint() to enable developers to more easily provide the CCS routing hint during authentication. See issue 2725
MSAL.NET provides helper methods to extract the authentication parameters from the WWW-Authenticate headers. This allows for dynamic scenarios such as claim challenge, Conditional Access Evaluation and Conditional Access authentication context scenarios. See https://aka.ms/msal-net/wwwAuthenticate and issue #2679 for details.
WAM support is now generally available in MSAL.NET. WithExperimentalFeatures() is no longer required to authenticate with WAM. See https://aka.ms/msal-net-wam for more details
MSAL enables easier cache eviction by exposing SuggestedCacheExpiry which helps determine the cache eviction time for for client credentials scenarios. See issue #2486
MSAL now adds runtime information to logs enabling easier diagnosing of authentication issues on all platforms. See issue 2559
On-Behalf-Of flow logic now performs refresh token flow eliminating the need to call AcquireTokenSilent and GetAccounts in OBO scenarios. See issue #2623.
Added monitoring flags for global stats. See issue #2646.
MSAL.NET adds CCS routing information for interactive requests using client info.. See issue #2525 and PR #2687.
When doing a client credential flow with an authority specified at the request level, the region is used and not the public cloud as the authority, which results in a cache miss. See issue #2686 for details.
Improved logging for cache performance. See issues/PRs #2690, #2688, #2680, and #2678.
** Add Kerberos ticket support **, see AzureAD#2602 Added cancellation token to TokenCacheNotificationArgs, to allow apps to send cancellation token to Redis. See issue #2551 FindAccessToken now logs the number of access tokens. See issue #2417 MSAL now exposes AuthenticationResult.TokenType. See issue #2637 Introduce WithFederationMetadata option for IWA and Username/Password flows, allowing developers to inject the federation metadata XML document. See issue #2152 MSAL.NET now provides routing information to Cached Credential Service (CCS). See issue #2525
Improved search of metadata in the federation metadata XML during WS-Trust flows. See issue #2665
Fixed a bug where WithTenant is ignored. See issue #2543
Fixed a bug with UWP token caching not being thread safe. See issue #2616
Handle multiple work accounts on same machine with WAM. See issue #2615
Fix B2C failure when user flows/policies have a name containing a .. See issue #2444
Handle the scenario where TokenType is null. See issue #2636
Handle Unity Windows Standalone il2cpp: NotSupportedException. See issue #2586
MSAL Xamarin Android now opens EDGE browser for authentication with OpenWithChromeEdgeBrowserAsync. See issue #2399
Handle WAM failure after account picker shows up on Win Server 2016. See issue #2572
Updated the regional telemetry schema. See issue #2622
Added time metrics to AuthenticationResultMetadata, which includes total duration, time spent in HTTP, and duration of token cache callbacks. See pull request #2581.
Added telemetry data to requests sent to WAM. See issue #2562.
Added option to hide iOS security prompt for system browser for iOS 13+. See issues #2131, #114, #512.
Fixed parenting of WAM account picker control. See issue #2566.
Fixed an exception in console apps that use WAM when they are run directly as an executable. See issue #2608.
MSAL.NET now correctly does Base64 encoding instead of Base64 URL encoding when interacting with the broker. See issue #2554.
Added support for Proof Key for Code Exchange (PKCE) in confidential client authorization code flows. See issue #1473.
Removed iOS Xamarin workaround for background threads, as it's no longer needed with fixes done in Mono. See issue #2556.
PKeyAuth challenge is now correctly performed on .NET Core, .NET 5, and .NET Standard platforms. See issue #2363.
WebView2 embedded browser now works in an app that executes in a protected directory. See issue #2502.
MSAL.NET now redirects standard and error output streams when starting a system browser on Linux. See issue #2427.
Correct OS version is now sent in x-client-os header on .NET classic. See issue #2517.
Fixed a NotImplementedException when setting a ConnectionLeaseTimeout on Unity. See issue #2537.
Improved the error message when an app is unable to listen to system browser on localhost URL for interactive flow. See issue #2219.
MSAL.NET will now fall back to WebView1 if WebView2 is unavailable on .NET 5, .NET Core, and .NET classic. See issue #2495.
MSAL.NET now, by default, enables a partitioned token serialization cache for client credential flow to improve performance. See issue #2544.
MSAL.NET now validates the domain of a regionalized authority to enhance usability. See issue #2514.
Symbols are now published to //symweb. See issue #2497.
Added support for calling On-Behalf-Of flow for Service Principals. See issue #1845.
MSAL.NET now supports Prompt.Create, which is needed for the self-service sign-up experience with External Identities. See issue #2463 and documentation and learn more here about the different ways to control the user interaction.
MSAL.NET now suggests the correct redirect URI to use, if WAM was used with an incorrect URI. See issue #2358.
Redesigned support for calling regional token services to increase resilience and API simplicity. See issue #2508.
Custom Tabs now work correctly in Android 29+. See issue #2418.
MSAL.NET now honors the shouldClearExistingCache when deserializing a null or empty blob. See issues #2490 and #2216.
Updated token cache related telemetry. See issue #2406 for details.
Added support for WebView2. See issue #1398 and WebView2 wiki for details.
Added the ability to set a window title of a WebView2 window. See issue #2397 for details.
Added support for specifying a custom fixed version of WebView2 runtime. See issue #2446 for details.
Added helper methods for desktop apps. See issue #2459 for details.
Added refresh_in logic to On-Behalf-Of flows as was the other flows, to improve resilence. See issue #2389 for details.
Stopped using reflection to deserialize JSON to improve Unity apps built for UWP. See issue #2343 and Troubleshooting Unity for details.
Added additional logging when the cache is not serialized in confidential client apps to help choosing the right token cache serialization. See issue #2461 and Token cache serialization for details.
GetAccountsAsync() is now obsolete in confidential client apps as confidential client applications need to have one cache per account. Use GetAccountAsync(string). See issue #1967 for details.
Fixed System.InvalidOperationException when calling GetAccountAsync in a Xamarin Android app. See issue #2434 for details.
Fixed a bug when a WAM account picker window was not correctly parented to windows. See issue #2469 for details.
Fixed the behavior of WithAuthority(string) to correctly parse an authority string. See #2412 for details.
Improved .NET 5 support for older versions of Windows. See issue #2445 for details.
Added MSAL.NET assembly to rd.xml to enable MSAL.NET to work in optimized UWP apps. See issue #1617 for details.
Added additional code analyzers. See issue #2419 for details.
Improved documentation to support Android 11. See Xamarin Android 11 docs.
Updated communication mechanism used in brokered authentication on Android to improve reliability and avoid power optimization issues. See issue #2150.
MSAL.NET now has support for MSA-passthrough with WAM, See issue #2126.
MSAL.NET now logs telemetry for the cache refresh status, See issue #2356.
MSAL.NET now uses ClientID+tenantID instead of just ClientId in the computation of the SuggestedCacheKey for AcquireTokenForClient (client credentials). This helps keeping the cache smaller in multi-tenant confidential client applications., See issue#2381.
Fixed ArgumentNullException and improved resiliency when using RSACryptoServiceProvider on NetCore and NetStandard See issues #2342.
Removed "Unresolved P/Invoke" warning from UWP, See issue #2367.
Fixed issue where PKEY auth would fail if WithExtraQueryParams were used, See issue #2359.
MSAL.NET now advertises PKAuth support only on supported platforms. See issues #1849, #2302 for details.
Added support for embedded view for .NET 5.0 projects. See issue #2310 for details.
Improved handling of broker's power optimization exception in Xamarin Android. See issue #2144 for details.
Added an ability to disable legacy ADAL cache with WithLegacyCacheCompatibility(false). See issue #1770 for details.
WithClientAssertion allows specifying a delegate to set the assertions. See issue #2184 for details.
Account is not longer deleted from the MSAL cache when a bad_token response is received from the authentication server. See issue #2294 for details.
Minimum UWP target supported is now 10.0.0.0. See issue #2330 for details.
Fixed ArgumentNullException and improved resiliency when using RSACryptoServiceProvider. See issue #2189 for details.
Honoring a provided localhost redirect URI in WithRedirectUri. See issue #2167 for details.
WithPreferredAzureRegion allows specifying an option to fallback to global endpoint if the region lookup fails. See issue #2287 for details.
WithPreferredAzureRegion allows specifying a region to use. See issue #2259 for details.
Optimized IMDS calling logic during regional lookup. See issue #2177 for details.
WAM is enabled on net5.0-windows10.0.17763.0. See issue #2274 for details.
Regional lookup now correctly uses a global endpoint when WithPreferredAzureRegion is set to false after the initial lookup was done with a regional endpoint. See issue #2260 for details.
WAM can now be used in console apps. See issue #2196 for details.
WAM support is moved to a separate package, Microsoft.Identity.Client.Desktop, which fixes dependency issues during build. See issues #2299, #2300, #2247 for details.
In WAM, account picker is now correctly not used when AcquireTokenInteractive is called with the default OS account. See issue #2246 for details.
Added cache compatibility tests for MSAL.Node. See issue #2158 for details.
Fundamentals:
AcquireTokenForClient and AcquireTokenSilent have improved performance, especially for large token caches. See issue #2204 for details.
TokenCache notifications are not fired when the TokenCache is not serialized by developers, improving performance of all APIs utilizing the token cache.
MSAL .NET now logs to telemetry if the token cache is serialized. See issue #2185 for details.
Cleaner IntelliSense. See issue #2263 for details.
Bug Fixes:
MSAL .NET will not force the user to enter their credentials when logging-in with WAM. See issue #2233 for details.
MSAL .NET now throws an actionable error message when ROPC is attempted with MSA accounts. See issue #2169 for details.
MSAL .NET now supports WithForceRefresh as part of the AcquireTokenOnBehalfOfParameterBuilder. See issue #2232 for details.
Fix PlatformNotSupportedException in MacOS. See issue #2251 for details.
New Features: MSAL .NET no longer includes the ref assemblies, which are unsupported by older tools and custom build systems. See issue #2100 for details.
Experimental Features:
https://aka.ms/msal-net-experimental-features
Windows Account Manager (WAM) is now available on .NET classic. See issue #2181 for details and #2182, which includes a new static OperatingSystemAccount property on the PublicClientApplication to use the user signed-in on the Windows machine. More information here: https://aka.ms/msal-net-wam.
Proof of Possession (Signed HTTP Request) for confidential clients now support key management. See issue #2013 and https://aka.ms/msal-net-pop for details.
Proof of Possession (Signed HTTP Request) has been removed for public clients.
MSAL .NET includes a fallback in case calling the local instance metadata service fails due to an unsupported version. See issue #2055 for details.
MSAL .NET now sends the source of region discovery in the telemetry. See issue #2166 for details.
Bug Fixes:
MSAL .NET now sends no prompt value by default when doing interactive login with iOS and Android brokers. See issue #2133 for details.
MSAL .NET now includes more logging around Android broker to assist with troubleshooting. The new log information is available as PII logs. See issue #2151 for details.
Due to changes with the v3 B2C responses, MSAL was crashing due to a new unexpected error code format. MSAL .NET now sanitizes the error codes for HTTP header transport. See issue #1881 for details.
MSAL .NET now throws MsalUiRequiredException for more error codes coming from the Android broker. See issue #2140 for details.
On iOS, the SSO extension makes background requests, and the NSUrlConnection HttpClient cancels requests when the app moves to the background. MSAL .NET now sets the BypassBackgroundSessionCheck to false. See issue #2164 for details.
Fix badly named header on WsTrust. See issue #2193 for details.
New Features: Enable WAM integration for UWP apps experimentally. To provide feedback, please open an issue. For details see https://aka.ms/msal-net-wam.
Bug Fixes: Fix the URI for IMDS call to detect the region. This fixes the typo in the URI for local IMDS call which is made to detect the region for regional auth.
Bug Fixes: Add new constructors for AuthenticationResult for backwards compatibility purposes. This fixes an API breaking change introduced in MSAL 4.17 where a new param was added to the AuthenticationResult constructor without a default value and swapping the last two parameters. This fix ensures compatibility both with MSAL 4.16.x and before, and with MSAL 4.17 until 4.20.1.
Bug Fixes: Fixes the incompatibility of MSAL.NET 4.20 with .NET 5.0 by temporarily removing the WAM experimental support (for the moment, please use 4.20 if you are interested in WAM). For details see #2095.
New Features: MSAL now expose the configured certificate on Confidential Client Application. This helps manage multiple instances of Confidential Client Application. Experimental WAM integration on Windows for .NET classic, .NET core and UWP. See https://aka.ms/msal-net-wam.
Bug Fixes: Fix AcquireTokenByIntegratedWindowsAuthentication on .NET core. Reverted the HTTP client used on .NET core as it was not possible to use default authentication which is needed for WS-trust. See issue #1988. MSAL correctly returns errors when using Android broker. See issue #2062. Fix 2 problems with returning the status codes and exceptions when using Android broker. See issues #2062 and #2078. Throw a better error when some Facebook accounts cause MSAL to throw a state mismatch exception. See issue 1872 for details. MSAL now migrates the ADAL cache for multi-tenant scenarios. See issue #2090.
New Features: MSAL now adds telemetry data for the detected region. See issue #2018.
Bug Fixes: The creation of HTTPClient is now threadsafe. This will prevent threading issues MSAL.NET's HttpClient. See issue 2034. MSAL will now add missing data from broker communication issues, this will allow us to more easily diagnose broker authentication issues on Android. See issue 2045. MSAL now properly bypasses device auth challenges on mobile. This will allow users to bypass challenges when the web client cannot handle client TLS. See issue.
New Features: MsalServiceException now allows for the setting of the headers, the response body and the correlation id. This allows developers to more easily mock the MsalServiceException. See issue #1977 for details. MSAL now supports regionalization to keep traffic inside a geographical area. See issue #1956 for details. MSAL now supports Proof of Possession (POP) on confidential client applications. See issue #1946 for details.
Bug Fixes: When the parsing of a WsTrust error fails, MSAL will now return the entire body. This allows for a better understanding of the error. See issue #1984 for details. When creating an HttpClient we were forcing a ServicePointManager.DefaultConnectionLimit = 30. The fix removes the setting of the connection limit (though the max limit in the config setting is updated to 50 connections it's not set for net desktop and net core. See issue #1992. MSAL.NET now hides the Sign In Title bar in embedded webview sign-in on Android. See issue #2014 and #1927.
Bug Fixes:
ID token related information is no longer lost in the second call of AcquireTokenOnBehalfOf. Issue #1950 for details. AcquireTokenOnBehalfOf now respects the WithAuthority modifer enabling multi-tenant resources access. Issue for details.
New Features:
New enum TokenSource indicates the source of a token (cache, identity provider or broker). Issue for details
Bug Fixes:
Fix for CryptographicException when using CNG certificate. Added support for .net classic 4.6.1. Issue for details. Fix for ArgumentNullException thrown by MsalExtensionException constructor. Issue for details. Reduce response time for GetDeviceId. MSAL now will disable MATS telemetry if it is not configured. Issue for details. Fix for System.Net.HttpListenerException when system browser flow is cancelled. Issue for details.
Bug Fixes:
Improved error message for embedded webview http redirect failure. Issue for details SuggestedCacheKey property in TokenCacheNotificationArgs now works correctly in the case of AcquireTokenByAuthorizationCode. Issue for details.
New Features:
MSAL exposes a SuggestedCacheKey property in TokenCacheNotificationArgs. This property will help determine the token cache location in web site / web api / daemon app scenarios, making it easier to adapt MSAL's token cache to a general purpose distributed cache. Issue for details.
MSAL hardnes its HTTP stack to prevent port exhaustion. Before this improvement, MSAL would use an HttpClient object for each request. In high scale scenarios, this can lead to port exhaustion, as disposing of HttpClient does not release ports. With this improvement, MSAL uses a static HttpClient, which prevents port exhaustion, combined with platform specific techniques to respect DNS changes. This change affects .net classic and .net core implementations. Issue for details.
Bug Fixes:
MSAL no longer misses the cache when an empty scope is requested. Issue for details.
New Features:
MSAL has been upgraded to use Android X. MSAL.NET will now use the latest Android SDKs for it's Xamarin.Android platform. Issue for details.
GetAccounts() can now filter by user flow for B2C accounts. MSAL's GetAccounts() api will now allow you to pass in a user flow to filter B2C accounts when quering the cache. Issue for details.
Bug Fixes:
MSAL can now migrate from ADALV3 to MSALV3 when multiple resourceId's are used. MSAL will now ignore ADAL resource strings when fetching RT to enable migration from ADALV3 to MSALV3 cachetokens. Issue for details.
MSAL will now maintain the correlation ID of the authentication request with broker specific interactions throughout it's entire execution. Issue for details.
MSAL will now return the correct value for ExpiresOn in the authentication result during brokered authentication. Issue for details.
MSAL now has improved logic for AcquireTokenSilent(), GetAccounts() and RemoveAccount() during brokered authentication. During brokered authentication, MSAL will now check its local cache for tokens first before sending the silent authentication request to broker. GetAccounts() will now merge the accounts from the local MSAL and broker caches when returning results. RemoveAccount() will now remove the account from both the local cache and the broker cache. Issue for details.
MSAL now has better error reporting during Integrated Windows Authentication. MSAL will now return the error in the body on WsTrust parse errors. Issue for details.
MSAL will now handle null intents returned to SetAuthenticationContinuationEventArgs. MSAL will now handle null intents returned to SetAuthenticationContinuationEventArgs to avoid throwing null reference exceptions. Issue for details.
New Features:
**MSAL no longer calls the OIDC metadata endpoint, as it can infer the authorization and token URLs based on the authority URL. This will speed up token acquisition, especially for multi-tenant applications, as fewer network calls will be made. For details see Issue for details.
Client throttling extended support MSAL will throttle all /token calls during an event in which the server sends a Retry-After header, thus ensuring the Retry-After instruction is observed. MSAL will also throttle server requests that result in MsalUiRequiredException being thrown, for example when the user is required to perform MFA but the app keeps trying to acquire a token silently. For details see Issue for details.
Bug Fixes:
MSAL .NET now respects the ValidateAuthority=false flag. See Issue for details.
When the Android broker (Authenticator / Company Portal) is configured but it is not installed, MSAL should revert to using its own cache to try to perform the AcquireTokenSilent call. Issue for details.
New Features:
Client throttling is supported in Public Client Applications. MSAL will now implement client side throttling to reduce excessive authentication requests sent to the service: In the case where the Azure AD service replies with an HTTP error implying throttling, MSAL.NET now respects itself the delay imposed by the service by throwing an exception telling the application after which delay/when it will be able to acquire a token again without even attempting to call the service. For details see Issue for details.
MSAL now can perform device authentication on Desktop. On Operating systems prior to Windows 10 (Windows 7, 8, 8.1 and their server conterparts) MSAL.NET is able to perform device authentication using PKey Authentication. Issue for details.
Bug Fixes:
MSAL .NET would throw a null ref when no authentication type was specified when creating a confidential client application. MSAL .NET now verifies the developer has specified one client credential (client secret, certificate, or client assertion) when using a confidential client application. See Issue for details.
GetAccountsAsync() used to return 0 accounts when the broker was not installed (on Xamarin.Android). MSAL will now return accounts from the local MSAL cache when the broker is not installed and WithBroker(trus) is used. Issue for details.
New Features:
Integrated Windows Auth available on .NET Core on Windows without username. On .NET Core, for the Windows platforms, AcquireTokenByIntegratedWindowsAuthAsync(scopes) works without passing the username.
The scope parameter is now less strict in some of the AcquireTokenXXX methods. MSAL now allows developers to call AcquireToken* methods without scopes. MSAL continues to ask for "offline_access", "profile" and "openid" scopes, which makes token providers (AAD B2B, AAD B2C, ADFS) return Id Tokens, which contain user metadata. Some token providers continue to issue access tokens, which can be used to access the UserInfo metadata endpoint. Issue.
Bug fixes:
Fix potential cache consistency issues in multi-threaded environment. Synchronize token cache to avoid cache inconsistency where token cache is shared with many environments.
Fix null reference exception thrown by AcquireTokenForClient when using a cert in .cer format / without a private key. Issue.
Fix the spelling in API WithInstanceDicoveryMetadata. Marked the WithInstanceDicovery as deprecated and added WithInstanceDiscoveryMetadata to fix the spelling.
Fix MsalClientException UserMismatchSaveToken sometimes thrown in web apps. Fix the scenario where in web app / web api scenarios where a token cache was shared across multiple users, MSAL would sometimes throw an MsalClientException.
New Features:
MSAL.NET will now remove accounts from the cache that have expired refresh tokens. MSAL.NET will remove both the refresh token and the associated account if the suberror is "bad_token" to avaoid unnecessary calls to AzureAD. Issue.
MSAL.NET uses telemetry schema V2 MSAL.NET has been updated to use HTTP telemetry schema V2. Issue.
Bug Fixes:
When migrating a Xamarin application from ADAL.NET to MSAL.NET and preserving the keychain, a CryptographicException can be thrown from the BrokerKeyHelper. MSAL.NET now does the broker key keychain look up by Service and Account only. Issue.
WithProofOfPossession produces a token of type POP when it is expected to be PoP. MSAL.NET will now produce a token of type PoP when WithProofOfPossession() is used. Issue.
New Features:
MSAL.NET now allows configuration of instance metadata end-point. WithInstanceDicoveryMetadata method now allows developers to pass an Uri with metadata. Issue.
Bug fixes:
Client Credentials flow not working with ADFS 2019. MSAL.NET now uses the token endpoint as audience and adds x5t to the signed assertion it creates from a certificate. Issue. Certain error messages are not returned from the Android Broker. MSAL.NET now throws better exceptions that show the root cause of Android broker failures. Issue. WithProofOfPossesion not exposed on AcquireTokenSilent builder. MSAL.NET now exposes the WithProofOfPossesion call on AcquireTokenSilent Issue.
New Features:
Added support for Android Broker to MSAL.NET. MSAL.NET will now be able to take advantage of the brokered authentication scenarios using the Microsoft Authenticator and the Intune Company Portal. Learn how to levereage the broker here. See issue.
Added client capabilities support to MSAL.NET. Issue.
Bug Fixes: Wrong Authority created in CreateAuthorityForRequest. MSAL.NET now properly configures the authority when set from acquire Token apis and is not set on the application. Issue.
Bug Fixes:
When using .WithBroker(true), but no broker is installed on the device, MSAL.NET would throw a null ref. MSAL.NET now checks if the user is required to have their device managed, and if not, the user will be guided through the regular authentication process with no broker. If device mangagement is required, the user will be guided to the App Store to install the Authenticator App. See more details in the issue.
Starting with version 4.8.1, MSAL.NET would throw a MonoTouchException on iOS 10 and 11 devices. Starting with iOS 13 , all WKWebViews report their full page user agent as desktop, previously this was reported as mobile to the server. A check was added in 4.8.1 to switch to use macOS user-agent for all browsers by default. Now, for devices lower than iOS 13, this check will not occur. See issue for more details.
Fix a Null Reference bug in the main AcquireTokenInteractive scenario on Android. This is the reason why release 4.8.0 was unlisted from NuGet -Issue.
Change the internal serialization library logic to prevent Mono errors with DataContract serializers Issue.
Bug fix: Cannot acquire token in UWP app on HoloLens via a unity plugin as json serialization fails. Serialization now works properly in MSAL.NET. Issue.
AAD Security question registration page unresponsive in Android embedded webview. MSAL.NET now properly handles the andoid activity when using the embedded webview. Issue.
"offline_access" scope causes token cache misses. MSAL.NET now properly filters the cache during silent authentication. Issues.
Improved invalid client error message. MSAL.NET now has a better error message when an invalid client error is sent back from AAD. Issues.
New Features: MSAL.NET now supports Proof of Possession. The PublicClientApplication on every target has support for this. Issue.
Token cache serialization for Mac. MSAL.NET is now able to serialize and deserialize the token cache during authentication on MAC OS. Issues.
MSAL.NET now uses "mobile" configuration for iOS Xamarin embedded webview. MSAL.NET now properly uses the WKWebview on iPad when using the embedded webview. Issues.
Bug fix: **Interactive auth with Edge system browser sometimes hanged. Issue
New Features: Added Subject Name + Issuer authentication to the acquire token by authorization code and acquire token by refresh token flows with the WithSendX5C() api on the confidential client application. All confidential client authentication flows will now have access to this feature. Issue.
New Features:
MSAL .NET now stores the application token returned from the iOS broker (Authenticator). This may result in the user experiencing less prompts. Issue.
New TokenCacheNotificationArgs.IsApplicationCache property simplifies the development of token cache serialization. TokenCacheNotificationArgs now include a flag named IsApplicationCache, which disambiguates between the app token cache and the user token cache.
Bug Fixes:
- Device Code Flow would fail with a misleading error message if the app was misconfigured in the Azure Application Portal. MSAL.NET now provides a better error message. - #1407
- Setting a non tenanted authority when calling AcquireTokenXX is now ignored. #1456
- Setting an authority audience of
AzureADMyOrgand a tenant ID would fail. It's now possible to specify.WithAuthority(audience)and.WithTenantId()#1320
Fundamentals:
- Added tests which check cache format interoperability between MSAL Java and MSAL .NET.
See the MSAL .NET 4.6.0 blog post for more details.
Bug Fix:
- Starting in v4.5.0 of MSAL.NET, when using Xamarin Android, a System.TypeInitializationException would be thrown. This is due to the Resource.designer.cs class being included automatically by the MSBuildExtrasSdk. See MSAL.NET issue and Xamarin Android issue for details.
New Features: MSAL now supports the device code grant for ADFS 2019. #1403 MSAL now supports the device code grant for Microsoft personal accounts. #1367 MSAL.NET now sends telemetry data to the /token endpoint in regards to the error code of the previous request, if applicable. This will enable MSAL.NET to determine reliablity across public client application calls.
Bug Fixes:
- Customers reported a nonce mismatch error when signing in with the Authenticator app on iOS 13. The issue has been resolved and increased logging included in the iOS broker scenario. See issue for more details.
- On iOS 13, when using the system browser, authentication was broken. This was because Apple now requires a presentationContext when signing in with the system browser. More information on this requirement here. And more details in the issue.
- At times, MSAL.NET would randomly fail on UWP. MSAL.NET now implements retry logic and has improved logging around the cache in UWP. See this issue and this issue for more details.
- During a client credential flow, MSAL.NET would throw a client exception stating the users should not add their own reserved scopes. MSAL.NET now merges the scopes if they are already in the reserved list and does not throw. See issue for more details.
- At times, during an interactive authentication, MSAL.NET would throw an ArgumentNullException. MSAL.NET now checks for null values when handling the authorization result parsing. See issue for details.
Fundamentals:
- MSAL.NET now uses the new internal Lab API for automated and manual testing. Issue.
Bug Fixes:
- Ensures that MSAL.NET works fine with brokers on iOS 13. On iOS 13, iOS, the broker, may or may not return the source application, which is used by MSAL.NET to verify the response is coming from broker. To maintain secure calls, MSAL.NET will now also create a nonce to send in the broker request and will verify the same nonce is returned in the broker response in the case of a missing source application. Issue
- After MSAL.NET acquired a token for a user, and the user signed-out - remove account, MSAL.NET was attempting to acquire the token with the same tenant as the first account, instead of using the tenant specified in the authority when building the application. MSAL.NET now uses the specified tenant. Issue
- Claims are now sent to both the /authorize and /token endpoints. Issue
- MSAL.NET on Xamarin iOS now returns the top-level view controller, which allows calling AcquireAuthorizationAsync() with an app RootViewController as a UINavigationController with an empty navigation stack. See PR for more details
Experimental:
- MSAL.NET now provides two extension methods, enabling you to acquire an SSH certificate.
Bug Fixes:
- .WithCertificate with /common audience scenario was broken. Confidential Client authorization flow and OBO were not able to use certificates with the common authority set. More details here
- MSAL.NET no longer strips the port from the authority URI*. When passing your own authority uri which includes a port, MSAL used to strip out the port from the URI, making the authority unreachable. More details here
- Fixed a crash on Android when Chrome isn't installed on the device. Exception was NameNotFoundException: com.android.chrome. More details here
- ConfidentialClient built from options didn't allow certificates. When building a confidential client from options, MSAL was forcing developers to use a secret. More details here
- Login screen loses information on device orientation change on Android. Username used to be lost from embedded webview when rotating the device. More details here
New Features:
- Broker support for Xamarin iOS. MSAL.NET now supports brokered authentication with Xamarin iOS. For details see https:aka.ms/msal-net-brokers, along with code snippets, and more details in the 4.3 release blog post. For help migrating from ADAL.NET using iOS broker to MSAL.NET using iOS broker, see this page on migration.
Bug Fixes:
- MSAL.NET was adding an extra
/to the authority when using.WithAuthority(AzureCloudInstance azureCloudInstance, Guid tenantId). This resulted in an MsalServiceException: "AADSTAT9002: Tenantv2.0not found..." More details here. - Starting in MSAL.NET 4.0, a MsalClientException was thrown instead of a MsalServiceException in exceptions coming from the server. Details here.
- MSAL.NET required custom error handling when dealing with a network down error. This was especially problematic on Xamarin iOS and Android. Details here.
- MSAL.NET was not correctly catching a network down exception. MSAL.NET now catches the exception and sets it on the correct TaskCompletionSource object. More information here.
Bug Fixes:
- Fixed API availability of WithParentActivityOrWindow on ios/android/windows/mac. See this item
- Fixed System browser not on by default in iOS and Android. See this item
New Features:
- Allow users to specify their own instance metadata. For details see https://aka.ms/msal-net-custom-instance-metadata More information on this feature here
- AcquireTokenSilent should not make calls to the network More information on this feature here
- Improve CA Error Handling More information on this feature here
- AcquireTokenSilent access the cache too many times More information on this feature here
- Allow injecting the Parent Activity/Window in the Client Builder More information on this feature here
- Add framework and version to MsalException ToString() More information on this feature here
Bug Fixes:
- Resolved the "Key not valid for use in specified state" error when a certificate with a non-exportable key is used on .NET Framework 4.7.2+ More information on this feature here
- Cryptic exceptions when attempting IWA / UP / Device Flow with an app that isn't registered as a public client More information on this feature here
New Features:
- MSAL.NET now provides options to control the system web browser. From MSAL.NET 4.0.0, you have been able to use the interactive token acquisition with .NET Core, by delegating the sign-in and consent part to the system web browser on your machine. MSAL.NET 4.1, brings improvements to this experience by helping you run a specific browser if you wish, and by giving you ways to decide what to display to the user in case of a successful authentication, and in case of failure. More information about this feature here
- MSAL.NET now supports ClientAssertions. In order to prove their identity, confidential client applications exchange a secret with Azure AD. MSAL.NET 4.1 adds a new capabilities for this advanced scenario: in addition to
.WithClientSecret()and.WithCertificate(), it now provides three new methods:.WithSignedAssertion(),.WithClientClaims()and.WithClientAdditionalClaims(). More information on this feature here
Bug Fixes:
- When using the
ConfidentialClientApplicationOptionsand including, for exampleInstance = "https://login.microsoftonline.com/", MSAL.NET was concatenating the double-slash. MSAL.NET will now check for a trailing slash and remove it. There is no action needed on the part of the developer. See [#1196] for details. - When using ADFS 2019, if no login-hint was included in the call, a null ref was thrown. See [#1214] for details.
- On iOS, for certain older auth libraries, sharing the cache with MSAL.NET, there was an issue with null handling in json. The json serializer in MSAL.NET no longer writes values to json for which the values are null, this is especially important for foci_id. See [#1189] and [#1176] for details.
- When using
.WithCertificate()and/common/as the authority in a confidential client flow, the MSAL.NET was creating theaudclaim of the client assertion as"https://login.microsoftonline.com/{tenantid}/v2.0". Now, MSAL.NET will honor both a tenant specific authority and common or organizations when creating theaudclaim. [#891] - MSAL.NET will make network calls less often when developers call
GetAccountsAsyncandAcquireTokenSilent. AAD maintains an instance discovery endpoint which lists environment aliases for each cloud. In order to optimize SSO, MSAL fetches this list and caches it - MSAL has to make a network call even in simple cases likeGetAccontsAsync. This improvement bypasses the need for this network call if the environments used are the standard ones. This work is tracked by MSAL issue 1174
New Features:
- MSAL now supports ADFS 2019. You can now connect directly to ADFS 2019. This is especially important if you intend to write an app working with Azure Stack. For more details see ADFS support
- MSAL now provides asynchronous callbacks as part of the ITokenCache interface. See Asynchronous token cache serialization for more information, code snippets, and a link to a sample. MSAL issue 481
- .NET Core now supports interactive authentication. Given that .NET Core does not provide a Web browser control, until MSAL.NET 4.0, the interactive token acquisition was not supported. Starting from this release, you can now use AcquireTokenInteractive with MSAL.NET. For more information and code snippets, see .NET Core now supports interactive auth. MSAL issue
Breaking Changes in 4.0.0
- ITokenCache's responsibility splatted between ITokenCache and ITokenCacheSerializer. In order to enable the async methods you need to use to subscribe to cache events, we have rewritten the non-async ones by calling the async ones. While doing that we splatted the responsibility of the ITokenCache interface between ITokenCache which now contains the methods to subscribe to the cache serialization events, and a new interface ITokenCacheSerializer which exposes the methods that you need to use in the cache serialization events, in order to serialize/deserialize the cache. This API is experimental and may change in future versions of the library without a major version. See more information on the impact here
- Replace TelemetryCallback with TelemetryConfig. Until MSAL.NET 3.0.8, you could subscribe to telemetry by adding a telemetry callback .WithTelemetry(), and then sending to your telemetry pipeline of choice a list of events (which themselves were dictionaries of name, values). From MSAL.NET 4.0, if you want to add telemetry to your application, you need to create a class implementing ITelemetryConfig. MSAL.NET provides such a class (TraceTelemetryConfig) which does not send telemetry anywhere, but uses System.Trace.TraceInformation to trace the telemetry events. You could take it from there and add trace listeners to send telemetry. See Telemetry for more information and code snippets.
- In confidential client applications, MSAL.NET was not returning a URL in the
GetAuthorizationRequestUrlflow. MSAL.NET now returns a URL in both overloads ofGetAuthorizationRequestUrl. MSAL issues 1193 and issue 1184
Bug Fixes:
- In confidential client applications, MSAL.NET now sends the X5C via AcquireTokenSilent, as it does with AcquireTokenInteractive using the IClientAssertionCertificate overload. Msal issue 1149
- MSAL.NET now correctly handles the X509 cert on .NET Core. MSAL issue 1139
- MSAL.NET now resolves the TeamID in the Keychain Access Group for the default configuration. Keychain sharing groups should be prefixed with the TeamID. Now, if the developer does not explicitly set the keychain access group through the WithIosKeychainSecurityGroup api, MSAL.NET will use the default "com.microsoft.adalcache", appended with the TeamID. Previously the TeamID was not included.MSAL issue 1137
Bug Fixes:
- AcquireTokenSilent sometimes ignored the tenant constraint. If the same user acquired tokens from different tenants, MSAL.NET would return an account, regardless of the tenant. MSAL.NET now returns the token based on the tenant. MSAL issue #1123
- DeserializeMsalV3 on ITokenCache should have the option to clear the in memory cache. DeserializeMsalV3 is currently a merge operation with existing in-memory data. MSAL.NET now has the option to be able to clear the in memory state and then deserialize the content in. MSAL issue #1109
New Features:
- MSAL.NET now creates an HttpClient that uses the AndroidClientHandler for Android 4.1 and higher. See documentation for more information. MSAL issue #1076
Bug Fixes:
- When doing the ADAL.NET fallback from MSAL.NET, MSAL.NET was doing the lookup based on the account.HomeAccountId or requestParameters.LoginHint. In ADAL.NET an account will never have a HomeAccountId (by design), so lookup needs to happen by Account.UserName instead. MSAL.NET issue #1100
- AcquireTokenInteractive would throw a PlatformNotSupportException on NetCore when using CustomWebUI. MSAL.NET no longer throws an exception when using CustomWebUI on NetCore. MSAL issue #1058
Bug Fixes:
- Exception: Failure to parse missing json on first login [MSAL issue #1052](https://github.com/AzureAD/microsoft-authentication- library-for-dotnet/issues/1052)
- B2C ROPC support MSAL issue #926
- FOCI is hiding the true cause of refresh token failures MSAL issue #1067
Bug Fixes:
- ** AcquireTokenInteractive parent param is not intuitive** MSAL issue #918
Breaking Changes in 3.0.4-preview
- AcquireTokenInteractive now takes a single parameter - the scopes. A new builder method WithParentActivityOrWindow was introduced for passing in a reference to the UI object that spawns the UI (Activity, Window etc.).
New Features:
- MSAL now supports custom B2C domains. MSAL issue #1025
- MSAL now initializes an HttpClient with NSUrlSessionHnadler() for iOS 7+. MSAL issue #1019
Breaking Changes in 3.0.3-preview
- The ClientCredential class is obsolete. There is no longer a need for the ClientCredential class to be public. This class has been marked as obsolete. MSAL issue #1007
- The ApiConfig and AppConfig namespaces have been changed to the Microsoft.Identity.Client namespace for discoverability. This provides a better user experience when updating from MSALv2 to MSALv3.0.3x. MSAL issue #1006]
- Deprecate UIParent and move static classes to a more appropriate class (eg
IsSystemWebviewAvailable()). MSAL issue #1005 - Move all error codes to
MSAL.Error. MSAL issue #1004 - Deprecate the MSALv2 api. Move v2 api methods/properties to the migration aid and remove functionality. MSAL issue #1001
- The
Componentproperty is obsolete. MSAL now transmits client app name and version to authorization and token requests. MSAL issue #978
Bug Fixes:
- Interactive login from multiple clouds was failing due to instance discovery, as was GetAccounts. This is now fixed. MSAL issue 1048 and 1030
- MSAL was calling
DefaultRequestHeaderswhich is not thread safe and could result in AcquireTokenSilent being called from multiple places at the same time. MSAL issue #1014 - SourceLink is available again MSAL issue #953
bug fixes: UI can hang due to not having proper SynchronizationContext for UI interaction
New Features:
- Device Code supports both verification_url and verification_uri
- MsalError contains all the error messages
- MsalException and its derived exception can now be serialized to JSON and deserialized
- MSAL.NET for .NET Core moved to .NET Core 2.1.
- At both the app creation and the token acquisition, you can now pass extra query parameters as a string (in addition to a Dictionary<string,string> introduced in MSAL 3.0.0
- MSAL.NET symbols are now published to enable SourceLink support
Breaking Changes in 3.0.1-preview
- AcquireTokenSilent has two overrides that require you to pass-in the account or the loginHint
- SubError property removed from MsalServiceException
- merge removed from ITokenCache's DeserializeXX methods
- WithClaims removed from app creation. it is now available on the AcquireToken methods
- ICustomWebUi.AcquireAuthorizationCodeAsync now takes a cancellation Token
bug fixes: When the client id entered is invalid, the error messages can be better PublicClientApplicationBuilder.CreateWithApplicationOptions does not respect the audience ASWebAuthenticationSession is skipped due to AppCenter build flags
- For more info on the release, along with code samples, checkout https://aka.ms/msal-net-3x
Breaking changes in MSAL.NET 3:
UIBehaviorwas renamed toPrompt(breaking change)TokenCacheNotificationArgsnow surfaces anITokenCacheinstead of aTokenCache. This will allow MSAL.NET to provide, in the future, various token cache implementations.TokenCacheExtensionswas removed and its methods moved toITokenCache(this is a binary breaking change, but not a source level breaking change)- The
SerializeandDeserializemethods onTokenCacheExtention(which were serializing/deserializing the cache to the MSAL v2 format) were moved toITokenCacheand renamedSerializeMsaV2and `DeserializeV2
Changes related to improving app Creation and configuration MSAL issue
- New class
ApplicationOptionshelps you build an application, for instance, from a configuration file - New interface
IMsalHttpClientFactoryto pass-in the HttpClient to use by MSAL.NET to communicate with the endpoints of Microsoft identity platform for developers. - New classes
PublicClientApplicationBuilderandConfidentialClientApplicationBuilderpropose a fluent API to instantiate respectively classes implementingIPublicClientApplicationandIConfidentialClientApplicationincluding from configuration files, setting the targetted cloud and audience, but also setting per application logging and telemetry, and setting theHttpClient. - New delegates
TelemetryCallbackandTokenCacheCallbackcan be set at application construction - New enumerations
AadAuthorityAudienceandAzureCloudInstancehelp you writing applications for sovereign clouds, and help you choose the audience for your application.
Changes related to improving token acquisition, addressing issues 810, 635, 426, 799 :
ClientApplicationBasenow implementsIClientApplicationBaseand has new members:AppConfigof new typeIAppConfigcontains the configuration of the applicationUserTokenCacheof new typeITokenCachecontains the user token cache (for both public and confidential client applications for all flows, butAcquireTokenForClient)- New fluent API
AcquireTokenSilent
- New fluent API
PublicClientApplicationandIPublicClientApplicationhave four new fluent APIs:AcquireTokenByIntegratedWindowsAuth,AcquireTokenByUsernamePassword,AcquireTokenInteractive,AcquireTokenWithDeviceCode.ConfidentialClientApplicationhas new members:AppTokenCacheused byAcquireTokenForClient- Five new fluent APIs:
AcquireTokenByAuthorizationCode,AcquireTokenForClient,AcquireTokenOnBehalfOf,GetAuthorizationRequestUrl,IByRefreshToken.AcquireTokenByRefreshToken
- New extensibility mechanism to enable public client applications to provide, in a secure way, their own browsing experience to let the user interact with the Microsoft identity platform endpoint (advanced). For this, applications need to implement the
ICustomWebUiinterface and throwMsalCustomWebUiFailedExceptionexceptions in case of failure. This can be useful in the case of platforms which don't have yet a Web browser. For instance, the Visual Studio Feedback tool is an Electron application which uses this mechanism. MSAL issue MsalServiceExceptionnow surfaces two new properties:CorrelationIdwhich can be useful when you interact with Microsoft support.SubErrorwhich indicates more details about why the error happened, including hints on how to communicate with the end user. MSAL issue
Changes related to the token cache:
- New interface
ITokenCachecontains primitives to serialize and deserialize the token cache and set the delegates to react to cache changes - New methods
SerializeMsalV3andDeserializeMsalV3onITokenCacheserialize/deserialize the token cache to a new layout format compatible with other MSAL libraries on Windows/Linux/MacOS.
A few bug fixes:
- MSAL now handles B2C domains from sovereign clouds, including US Government, Blackforest, and Mooncake. B2C domains with *.b2clogin.us, *.b2clogin.cn, and *.b2clogin.de are now included in the MSAL allowed domain list for B2C authorities. MSAL issue
- Improved error message handling to detect issues faster and not hit null reference exceptions. Sometimes, for example, when the instance discovery endpoint is not found, the Oauth2Client in MSAL would hit a null reference exception. MSAL now detects such issues faster and returns a more meaningful error message (e.g. the http response code).
- MSAL integrates SourceLink https://github.com/dotnet/sourcelink. This allows MSAL to embed pdb files and source code in the NuGet package, allowing users to debug into MSAL without replacing their package reference with a project reference. MSAL PR
- MSAL.NET now supports Xamarin.Mac. We now ship another MSAL assembly, that can be used when building apps using Xamarin.Mac. MSAL.NET for Xamarin.Mac supports interactive authentication via an embedded browser, as well as silent authentication. It does not serialize its token cache to the keychain, instead users are asked to provide their own serialization mechanism as they see fit. A keychain based implementation will likely be implemented in a future release. MSAL PR
- Easier migration from ADALv2 to MSALv2 due to a new AcquireTokenFromRefreshToken API. ADAL.NET v2.x exposes the refresh token in the
AuthenticationResult, as well as methods to acquire a token from a refresh token in theAuthenticationContext. Through theConfidentialClientApplication, MSAL now implements an explicit interface to help customers migrate from ADAL v2 to MSAL v2. With this method, developers can provide the previously used refresh token along with any scopes. The refresh token will be exchanged for a new one and cached. Please see https://aka.ms/msal-net-migration-adal2-msal2 for more details. MSAL issue - Token cache account was not being deleted on Android platform. MSAL PR
- When using ADAL v4.4.2 and MSAL v2.6 in the same Xamarin project, an error would result of
Cannot register two managed typesdue to the iOS view controllers being registered under the same name. Now the MSAL iOS view controllers are prefixed withMSALso they are distinct from the ones in ADAL. MSAL issue - When using the
KeychainSecurityGroupproperty to enable application sharing of the token cache, developers were required to include the TeamId. Now, MSAL resolves the TeamId at runtime. A new propertyiOSKeychainSecurityGroupshould be used instead. See https://aka.ms/msal-net-ios-keychain-security-group for details. MSAL issue
Move AuthenticationContinuationHelper class back to the Microsoft.Identity.Client namespace to avoid breaking changes to existing apps.
- Setting ForceRefresh = true in AcquireTokenSilent used to skip access token cache lookup MSAL now handles ForceRefresh=true correctly and circumvents looking up an access token in the cache, instead using the refresh token to acquire a new access token. MSAL issue #695
- Ensured cache lookup filters on the specified tenantId, otherwise the cache lookup would always find the token for the home tenant This enables MSAL to acquire tokens for resources outside the home tenant. MSAL issues #694
- For more info on the release, see https://aka.ms/msal-net-2-6 for details
- Improved error messages for Integrated Windows Auth: MSAL now returns better error messages for managed users using Integrated Windows Auth. ADAL issue #1398
- New parameter for UIBehavior: B2C developers can now use NoPrompt as a UIBehavior. For example, when envoking the edit profile policy to avoid the account selection UI and move directly to the edit profile UI. MSAL issue #588
- UIParent is available on all platforms: The UIParent constructor now takes in (object parent, bool useEmbeddedWebview) and is available on all platforms. MSAL issue #676
- Remove dependency on Newtonsoft.Json: MSAL now uses Microsoft.Identity.Json MSAL PR
- Deprecate
HasStateChanged: MSAL was not using this flag, so it has been deprecated ADAL issue #1186 - Obsolete public WebUI net45 types from Internal.UI namespace: MSAL
- NetStandard Unification: MSAL.NET helps you build multi-platform applications more easily by rationalizing the .NET Standard 1.3 platform. For details see blog post about this release available from: https://aka.ms/msal-net-2-6
- Public namespace change: If you implement dual serialization (AdalV3/Unified cache), and therefore are using Microsoft.Identity.Core.Cache to access some of the public cache classes, please note the namespace has changed to Microsoft.Identity.Client.Cache. You will get this error when updating packages: The type or namespace name 'Core' does not exist in the namespace 'Microsoft.Identity' (are you missing an assembly reference?). Just replace Core with Client in the using statement.
- Move MSAL code to the MSAL repo
- Improved the testability of apps using MSAL.NET: MSAL.NET was not easily mockable because the AuthenticationResult was an immutable sealed class with no public constructors. AuthenticationResult now has a public constructor for testing. MSAL issue #682
- Improved support for Azure AD B2C: apps constructors now understand to b2clogin.com based authorities, Developer no longer needs to set ValidateAuthority=false, as the library handles this now. MSAL issue #686
- GetAccountsAsync() can now be called when the device / computer is offline. It was making an network call to the instance discovery endpoint to determine the environments (equivalent clouds base URLs) for caching, which meant GetAccountsAsync() did not work off-line. This has been fixed and GetAccountsAsync() is not dependent on a network call and works off-line. MSAL issue #630
Hot fix release includes:
- Fix performance issue [1406] for degredation in .NET Framework compared to .NET Core
Improvements and fixes to the token cache
- The serialized token cache can now be shared by different applications, therefore providing SSO if the same user signs-in in both applications
- See PR and MSAL Issue #653
- On .NET Core, the Token cache was shared by all instances of applications in memory. This is now fixed (See MSAL.NET issue #656 and PR)
- Fixes consistency issues for advanced token cache migration scenarios from ADAL v3.x to ADAL v4.x to MSAL v2.x
- Cache lookups were optimized. Work done in conjunction with ADAL.iOS and MSAL.iOS native) PR
More browsers are now supported on Xamarin.Android when you choose to use system web browsers.
- Removed chrome dependency for system browser on Android devices. See https://aka.ms/msal-net-system-browsers for more information. MSAL issue #664
Azure AD B2C improvement
- Add support for b2clogin.com for b2c authorities MSAL issue #669 #632
This release includes:
- Fix for device code flow where server is now expecting device_code as the body parameter.
This release includes:
- Fix for cross-thread exception when setting the ownerWindow ADAL issue #1277
- Ensure error codes are public MSAL issue #638
- Add device code flow api to iOS and Android platforms MSAL issue #642
This release contains bug fixes on top of MSAL 2.2.0-preview:
- Due to static initialization, there was a race condition which appeared randomly. MSAL issue #629
- For iOS, TeamId is now accessible when the device is locked. MSAL issue #626
- For iOS, MSAL returns a useful error message, and an aka.ms link, when keychain access groups have not been set in the Entitlements.plist. MSAL issue #633
- Cache serialization for .NetCore
- Improve logging for device code flow to handle "authorization_pending" exceptions as info messages MSAL issue #631
- MSAL.NET 2.2.0 now supports Device Code Flow. For details see https://aka.ms/msal-device-code-flow
- Xamarin.iOS applications using the system web view now benefit from the integration with SFAuthenticationSession for iOS11 and ASWebAuthenticationSession for iOS12+ MSAL issue 489
- A clear MsalClientException message is now returned when the application is not able to access keychain, with instructions. See https://aka.ms/msal-net-enable-keychain-access for details.
- Removed double-logging in log files and callbacks. AzureAD/azure-activedirectory-library-for-dotnet#1289
- Improved 429 server error handling by exposing the Http Response headers in MsalServiceException. See https://aka.ms/msal-net-retry-after
- UWP cache fix. The key of the storage on UWP should be 255 characters or less. When using several scopes the key could exceed 255 characters. Now hashing scopes and environment on UWP. 612
- Integrated Windows Authentication and Username / Password authentication flows. For details see https://aka.ms/msal-net-iwa and https://aka.ms/msal-net-up
This release contains bug fixes on top of MSAL 2.0.0-preview:
- When using MSAL 2.0.0-preview with Azure AD B2C, the cache was never hit. (See MSAL#604), and the accounts were not removed correctly (See MSAL #613)
- The TokenCacheExtensions.Deserialize was throwing if a null array of bytes was passed as arguments instead of silently not doing anything. (See MSAL #603)
- When migrating a token cache from ADAL v3 or ADAL v4 to MSAL 2.0, the override of acquire token silent without authority used to work incorrectly (cache was missed)
This release contains:
- Remove support for Windows 8/8.1 and Windows phone 8/8.1
- Add support for .NETCore (Netcoreapp1.0 for portable desktop and web apps) and Uap10.0 for Windows 10 Applications
- Define the notion of Account (through the IAccount interface), instead of User. This breaking change provides the right semantics: the fact that the same user can have several accounts, in different Azure AD directories.
- The methods and properties returning IAccount are now all asynchronous, as in some cases getting the information might require querying the identity provider.
- The types that had fields or properties of type IUser in MSAL.NET 1.x now reference IAccount.
- In the Xamarin.iOS platform, PublicClientApplication has a new property named KeychainSecurityGroup. This Xamarin iOS specific property enables you to direct the application to share the token cache with other applications sharing the same keychain security group. If you provide this key, you must add the capability to your Application Entitlement. For more info, see https://aka.ms/msal-net-sharing-cache-on-ios. This API may change in a future release.
- In the previous versions of MSAL.NET, Xamarin.Android and Xamarin.iOS used the System web browser interacting with Chrome tabs. This was great if you wanted to benefit from SSO, but that was not working on some Android phones which device manufacturers did not provide Chrome, or if the end user had disabled Chrome. As an app developer, you can now leverage an embedded browser. To support this, the UIParent class now has a constructor taking a Boolean to specify if you want to choose the embedded browser. It also has a static method, IsSystemWebviewAvailable(), to help you decide if you want to use it. For more details about this possibility see the article in MSAL’s conceptual documentation: https://aka.ms/msal-net-uses-web-browser. Also the web view implementation might change in the future
- If migrating from MSAL 1.x to MSAL 2.x, you’ll get a number of compilation errors, but they are pretty straightforward to fix. In most cases you will only need to:
- Replace IUser by IAccount
- Replace the calls to application.Users to asynchronous calls to application.GetAccountsAsync
- In advanced multi-account applications, where you were using the IUser.Identifier, you will now need to use the IAccount.HomeAccount.Identifier. We have provided meaningful and actionable compiler errors that will tell you exactly what to do and will link to documentation to help you migrate.
- To preserve the single-sign-on (SSO) state, the new versions of ADAL(v4) and MSAL(v2) share the same token cache, are capable of reading the ADAL 3.x token cache and are capable of writing the ADAL 3.x token cache in addition to the new cache format (named unified cache), see https://aka.ms/adal-net-to-msal-net.
- For more info on the release, checkout https://aka.ms/msal-net-2-released
Hot fix of null pointer in iOS TokenCacheAccessor(#570)
This release contains updates to Xamarin.Android.Support v27.0.2 and MonoAndroid8.1 (#553 #520).
This release fixes references issues for Xamarin Android (for instance #520 & #524). When you create a new Xamarin Forms project and reference MSAL this now works out of the box. If you want to migrate an existing project to MSAL 1.1.2, please read this [wiki] (https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/Troubleshooting-Xamarin.Android-issues-with-MSAL) page.
This release contains -
- Added support to use RSACng in .net 4.7 (#448)
- Expose claims as an attribute for MSALUiRequiredException (#459)
- Updated Xamarin Forms Android support libraries to 25.3.1 (#450)
- Added Arlington URL to list of trusted authorities (#495)
- Changes for GDPR complicance with PiiLogs (#492)
- Several bug fixes
This release marks the seconds preview of the library which brings in several features and changes -
- Support for NetStandard
- Client Certificate Assertion in NetCore
- Support for system webviews in iOS/Android
- Updated Object Model
- Updated to JSON cache storage
- Several bug fixes