fix(proxy): allow org admins past route gate for team update/delete/block/unblock

Add these routes to self_managed_routes so non-proxy-admin callers reach
handlers that already enforce access via _verify_team_access. The org-admin
branch in non_proxy_admin_allowed_routes_check requires organization_id in
the JSON, which team update/delete/block/unblock typically omit.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Milan 2026-05-08 20:08:56 +03:00
parent 98cd057f38
commit 8e7178aaf8
No known key found for this signature in database

View file

@ -691,6 +691,14 @@ class LiteLLMRoutes(enum.Enum):
"/team/member_add",
"/team/member_delete",
"/team/member_update",
# Team lifecycle writes: handlers call _verify_team_access (proxy admin,
# team admin, or org admin of the team's org). Route-level org-admin
# detection only inspects organization_id in the body, which these
# payloads often omit, so they must be self-managed like member_*.
"/team/update",
"/team/delete",
"/team/block",
"/team/unblock",
"/team/permissions_list",
"/team/permissions_update",
"/team/daily/activity",