MSAL.NET 4.11.0

4.11.0

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

• WithProofOfPosession produces a token of type POP when it is expected to be PoP MSAl.NET will now produce a token of type PoP when WithProofOfPosession() is used. Issue

4.10.0

4.10.0

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 Andorid Broker MSAL.NET now throw 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 builder 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

MSAL.NET 4.9.0

4.9.0

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. Issue
• Added client capabilities support to MSAL.NET Issue

Bug Fixes:

• Wrong Authority created in CreateAuthorityForRequest MSAL.NET now properly creates B2C authorities when using the CreateAuthorityForRequest() API. Issue

MSAL.NET 4.8.2

4.8.2

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. #1598 .
• 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. #1621

4.8.1

Bug fixes:

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 - #1585

Change the internal serialization library logic to prevent Mono errors with DataContract serializers - #1586

MSAL.NET 4.8.0

4.8.0.

Bug fix:
Cannot acquire token in UWP app on HoloLens via a unity plugin as json serialization fails MSAL now uses Newtonsoft.Json for serialization. Issue

AAD Security question registration page unresponsive in Android embedded webview MSAL now properly handles the andoid activity when usin the embedded webview. Issue

"offline_access" scope causes token cache misses MSAL now Proberly filters the cache during silent authentication. Issues

Improved invalid client error message MSAl 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 is now able to serialize and deserialize the token cahce auring authentication on MAC OS. Issues

MSAL now uses "mobile" configuration for iOS Xamarin embedded webview MSAl now properly uses the MKWebview on iPad when using the embedded webview. Issues

MSAL.NET 4.7.1

Bug fix
Interactive authentication with Edge as a system system browser sometimes hanged. Issue #1506

MSAL.NET Version 4.7.0

4.7.0

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 acces to this feature. Issue

4.6

4.6.0

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 AzureADMyOrg and 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.

4.5.1

4.5.1

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.