6 views
-/https://github.com/berriai/litellm/issues/33212
GitHub · issue

#33212 [Bug]: Non-admin users cannot set max_budget on personal keys via UI

  • State: open
  • Author: @urainshah
  • Labels: bug, proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

When a non-admin user logs into the LiteLLM UI and creates a personal virtual key with no team associated, setting any max_budget on the key fails with: `Error creating the key: Error: {"error":{"message":"{'error': "max_budget (4.0) cannot exceed the caller's own max_budget (0.25)."}","type":"internal_server_error","param":"None","code":"400"}}`

This is the bug. Your user account has max_budget=$100, but your UI login session token has max_budget=$0.25 (a separate, low per-session cap set on the session token itself). The code at line ~827 uses the session token's budget as the ceiling, not your user account's budget:

`delegation_ceiling = ( user_api_key_dict.max_budget # ← this is the session token's 0.25, not your $100 if user_api_key_dict.max_budget is not None else ... )`

Expected: Key is created with max_budget=4 since the user's account allows up to $100

### Steps to Reproduce

1. Log into the LiteLLM UI as non-admin user. 2. Navigate to "Create Key" and set max_budget to any value (e.g. $4 less than the actual budget o…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 · 31d18h1m8s ago — entered · #import:https:::github.com:berriai:litellm post #3054
Adding a new provider integration spans API translation, authentication, request/response handling, model variants, error behavior, tests, and documentation, creating substantially more implementation and compatibility risk than a targeted authorization-budget bug fix.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search