timoklimmer / powerproxy-aoai

Monitors and processes traffic to and from Azure OpenAI endpoints.
MIT License
85 stars 24 forks source link

Bump azure-identity from 1.14.1 to 1.15.0 #28

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 8 months ago

Bumps azure-identity from 1.14.1 to 1.15.0.

Release notes

Sourced from azure-identity's releases.

azure-identity_1.15.0

1.15.0 (2023-10-26)

Features Added

  • Added bearer token provider. (#32655)

Bugs Fixed

  • Fixed issue InteractiveBrowserCredential does not hand over to next credential in chain if no browser is supported.(#32276)

azure-identity_1.15.0b2

1.15.0b2 (2023-10-12)

Features Added

  • Added enable_support_logging as a keyword argument to credentials using MSAL's PublicClientApplication. This allows additional support logging which may contain PII. (#32135)

Breaking Changes

These changes do not impact the API of stable versions such as 1.14.0. Only code written against a beta version such as 1.15.0b1 may be affected.

  • Windows Web Account Manager (WAM) Brokered Authentication is moved into another package.

Bugs Fixed

  • ManagedIdentityCredential will now correctly retry when the instance metadata endpoint returns a 410 response. (#32200)

azure-identity_1.15.0b1

1.15.0b1 (2023-09-12)

Features Added

  • Added Windows Web Account Manager (WAM) Brokered Authentication support.
  • Added enable_msa_passthrough suppport for InteractiveBrowserCredential. By default InteractiveBrowserCredential only lists AAD accounts. If you set enable_msa_passthrough to True, it lists both AAD accounts and MSA outlook.com accounts that are logged in to Windows.

Bugs Fixed

  • Ensure AzurePowershellCredential calls PowerShell with the -NoProfile flag to avoid loading user profiles for more consistent behavior. (#31682)
  • Fixed an issue with subprocess-based developer credentials (such as AzureCliCredential) where the process would sometimes hang waiting for user input. (#31534)
  • Fixed an issue with ClientAssertionCredential not properly checking if CAE should be enabled. (#31544)
  • ManagedIdentityCredential will fall through to the next credential in the chain in the case that Docker Desktop returns a 403 response when attempting to access the IMDS endpoint. (#31824)

Other Changes

  • Update typing of async credentials to match the AsyncTokenCredential protocol.
  • If within DefaultAzureCredential, EnvironmentCredential will now use log level INFO instead of WARNING to inform users of an incomplete environment configuration. (#31814)
  • Strengthened AzureCliCredential and AzureDeveloperCliCredential error checking when determining if a user is logged in or not. Now, if an AADSTS error exists in the error, the full error message is propagated instead of a canned error message. (#30047)
  • ManagedIdentityCredential instances using IMDS will now be allowed to continue sending requests to the IMDS endpoint even after previous attempts failed. This is to prevent credential instances from potentially being permanently disabled after a temporary network failure.
  • IMDS endpoint probes in ManagedIdentityCredential will now only occur when inside a credential chain such as DefaultAzureCredential. This probe request timeout has been increased to 1 second from 0.3 seconds to reduce the likelihood of false negatives.
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.


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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)