Skip to main content
LiteLLM is moving to Rust Read the latest updates.

LiteLLM v1.109.1 and v1.110.0rc2 refuse Azure login fields in the body

Deploy this version​

docker run \
-e LITELLM_MASTER_KEY=sk-<paste-a-long-random-key> \
-e DATABASE_URL=postgresql://<user>:<password>@<host>:5432/<dbname> \
-e STORE_MODEL_IN_DB=True \
-p 4000:4000 \
docker.litellm.ai/berriai/litellm:1.110.0-rc.2

This release is published as ghcr.io/berriai/litellm:v1.110.0-rc.2. See the GitHub release and the full releases page.

The published GitHub tag is v1.110.0-rc.2. These notes compare it with v1.110.0-rc.1, the previous release candidate on rc/1.110.0. It is a small rc patch with one change backported onto the rc branch, and everything else is unchanged from v1.110.0-rc.1, whose release notes cover the full 1.110 line. There are no new database migrations. The v1.110.0-rc.2 tag points at bf3cb0c.

Breaking Changes
  • Keys, teams and auth: Move tenant_id, client_id, client_secret, azure_username, azure_password and azure_scope request tags into metadata - PR #51254, also in v1.106.9, v1.108.6 and v1.109.1

What's Changed​

  • Keys, teams and auth: Changed model and pass-through routes to refuse body client_id, client_secret, tenant_id and Azure login fields - PR #51254, also in v1.106.9, v1.108.6 and v1.109.1

The change is backported in PR #51263.

Full Changelog​

https://github.com/BerriAI/litellm/compare/v1.110.0-rc.1...v1.110.0-rc.2

LiteLLM Enterprise
SSO/SAML, audit logs, spend tracking, multi-team management, and guardrails, built for production.
Learn more →