19 views
-/https://github.com/berriai/litellm/issues/20494
GitHub · issue

#20494 [Bug]: generating new key with same secret key doesn't throw error

  • State: open
  • Author: @curious-broccoli
  • 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?

Calling /key/generate with the same secret key as an existing one doesn't throw an error. While it is probably not too likely that this happens to someone, it should still return an error.

### Steps to Reproduce

1. Call /key/generate with ``` { "key_alias": "test duplicate" } ``` 2. Call it again (replace placeholder) ``` { "key_alias": "test duplicate 2", "key": "[placeholder for value of "key" from previous response]" } ``` 3. Only the first key exists now although second response returned 200 and also the correct name

### Relevant log output

```shell 1st response:

{ "key_alias": "test duplicate", "duration": null, "models": [], "spend": 0.0, "max_budget": null, "user_id": null, "team_id": null, "max_parallel_requests": null, "metadata": {}, "tpm_limit": null, "rpm_limit": null, "budget_duration": null, "allowed_cache_controls": [], "config": {}, "permissions": {}, "model_max_budget": {}, "model_rpm_limit": null, "model_tpm_limit": null, "guardrails": null, "prompts": null, "blocked":…

GitHub resolver

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

Refresh page
vote history (1 events)
#0 of 0 · 31d18h41m43s ago — entered · #import:https:::github.com:berriai:litellm post #2273
The right-side work spans a new provider integration, AWS authentication and protocol handling, shared search abstractions, interception pathways, compatibility behavior, and broader testing. The left-side work is comparatively localized to request validation and persistence/error handling, with limited regression scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search