BerriAI/litellm · error · HTTPException
Failed to update JWT key mapping.
Error message
Failed to update JWT key mapping.
What it means
Error "Failed to update JWT key mapping." thrown in BerriAI/litellm.
Source
Thrown at litellm/proxy/management_endpoints/jwt_key_mapping_endpoints.py:144
cache_key = f"jwt_key_mapping:{updated_mapping.jwt_claim_name}:{updated_mapping.jwt_claim_value}"
await user_api_key_cache.async_delete_cache(cache_key)
return _to_response(updated_mapping)
except HTTPException:
raise
except Exception as e:
error_str: Final = str(e).lower()
if "unique" in error_str or "p2002" in error_str:
raise HTTPException(
status_code=409,
detail="A mapping with those claim values already exists.",
)
if "foreign" in error_str or "p2003" in error_str:
raise HTTPException(
status_code=400,
detail="The provided key does not match an existing virtual key.",
)
raise HTTPException(status_code=500, detail="Failed to update JWT key mapping.")
@router.post("/jwt/key/mapping/delete", tags=["JWT Key Mapping"])
async def delete_jwt_key_mapping(
data: DeleteJWTKeyMappingRequest,
user_api_key_dict: UserAPIKeyAuth = Depends(user_api_key_auth),
):
from litellm.proxy.proxy_server import prisma_client, user_api_key_cache
if user_api_key_dict.user_role != LitellmUserRoles.PROXY_ADMIN:
raise HTTPException(status_code=403, detail="Only proxy admins can delete JWT key mappings")
if prisma_client is None:
raise HTTPException(status_code=500, detail="Database not connected")
try:
# Get old mapping for cache invalidation
old_mapping: Final = await JWTKeyMappingRepository(prisma_client).table.find_unique(where={"id": data.id})View on GitHub (pinned to 77b7c6c40c)
Solutions
- Check proxy logs for the underlying database error.
- Verify the mapping ID exists and the database connection is healthy, then retry.
When it happens
Trigger: Thrown at litellm/proxy/management_endpoints/jwt_key_mapping_endpoints.py:144 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of BerriAI/litellm@77b7c6c40c (2026-08-18).
Data as JSON: /api/errors/ea205ccd528a7775.
Report an issue: GitHub.