Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump Microsoft.Identity.Client from 4.16.0 to 4.16.1 #255

Merged

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps Microsoft.Identity.Client from 4.16.0 to 4.16.1.

Release notes

Sourced from Microsoft.Identity.Client's releases.

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
Changelog

Sourced from Microsoft.Identity.Client's changelog.

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:

MSAL no longer misses the cache when an empty scope is requested. Issue for details

4.15

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

4.14.0

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

Commits

Dependabot compatibility score

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)

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Jul 13, 2020
@dependabot-preview dependabot-preview bot merged commit befb51b into master Jul 13, 2020
@dependabot-preview dependabot-preview bot deleted the dependabot/nuget/Microsoft.Identity.Client-4.16.1 branch July 13, 2020 06:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants