Bump Microsoft.Identity.Client from 4.10.0 to 4.18.0 in /src/02-Corporate

[dependabot-preview]

Bumps Microsoft.Identity.Client from 4.10.0 to 4.18.0.

Release notes

Sourced from Microsoft.Identity.Client's releases.

4.18.0

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.

4.17.1

Bug Fixes:

ID token related information is no longer lost in the second call of AcquireTokenOnBehalfOf [Issue #1950 for details](AzureAD/microsoft-authentication-library-for-dotnet#1950) AcquireTokenOnBehalfOf now respects the WithAuthority modifer enabling multi-tenant resources access Issue for details

4.17.0

New Features:

Addition of an enum TokenSource to indicate the source of a token which can be 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

4.16.1

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

4.16.0

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

MSAL.NET 4.15.0

4.15.0

Changelog

Sourced from Microsoft.Identity.Client's changelog.

4.18.0

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.

4.17.1

Bug Fixes:

ID token related information is no longer lost in the second call of AcquireTokenOnBehalfOf. [Issue #1950 for details](AzureAD/microsoft-authentication-library-for-dotnet#1950) AcquireTokenOnBehalfOf now respects the WithAuthority modifer enabling multi-tenant resources access. Issue for details

4.17.0

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

4.16.1

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

4.16

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:

Commits

• 57c5a24 Add regional support with experimental flag (#2025)
• a7d59f0 Add the default constructor (#2022)
• 55bd0e7 changelog 4.18 (#2021)
• c20b385 Fixing artifact path (#2020)
• 4cef956 remove "sign-in" hard-coded in android embedded webview (#2019)
• d4f0a03 Nebharg/regional auth support (#2016)
• 4010442 Pop implementation for Confidential Client (#1986)
• 59fb140 Add regional support (#1972)
• ab09d1f Improve logging performance around token cache (#2010)
• cd4ebe0 Do not run cache compat tests twice
• Additional commits viewable 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.

---

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)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #63.