Bump Microsoft.Identity.Client from 4.8.0 to 4.8.1

[dependabot-preview]

Bumps Microsoft.Identity.Client from 4.8.0 to 4.8.1.

Release notes

Sourced from Microsoft.Identity.Client's releases.

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

Changelog

Sourced from Microsoft.Identity.Client's changelog.

4.8.1.

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

4.7.1.

Bug fix: **Interactive auth with Edge system browser sometimes hanged. Issue

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

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.

4.5.0

... (truncated)

Commits

• bedc8a2 Fix #1586 - add correct Preserve attribute (#1599)
• bb65754 Add [Preserve] attributes for linking and more logging for test (#1596)
• 0408eb0 fix for null ref during interactive flow w/out android broker (#1589)
• c6ac5ca Update changelog for MSAL 481 (#1584)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

If all status checks pass Dependabot will automatically merge this pull request.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)