4.23
4.23.0
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.