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

#32375 [Feature]: Key rotation UX — email alerts, SSO gate for auto-rotation, suppress misleading decrypt errors

  • State: open
  • Author: @krrish-berri-2
  • Labels: enhancement, proxy

## Summary

Master key and virtual key rotation currently have no notification mechanism and produce misleading log output. This creates operational pain for admins and end users.

### 1. Email alerts on key rotation

When a virtual key is regenerated (`POST /key/regenerate`), the key owner receives no notification — they just discover their key stopped working. The new key value is only returned in the API response to the admin who triggered the rotation.

**Proposal:** Send an email notification to the key owner containing the new key value (or a link to retrieve it from the UI). For master key rotation, send a confirmation to the admin.

### 2. Auto-rotation should require SSO/SCIM

If auto-rotation is enabled for virtual keys, there's no way to deliver the new key to the user unless we have their email. Without SSO/SCIM configured, users may not have an email on file.

**Proposal:** Gate the auto-rotation feature behind SSO/SCIM configuration. If no SSO is configured, auto-rotation should be disabled (or warn the admin) since there's no reliable way to notify key owners of the new key.

### 3. Default email alerts for SSO/SCIM users on auto-rotation

When SSO/SCIM is configured…

GitHub resolver

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

Refresh page
vote history (2 events)
#0 of 0 · 31d18h58m37s ago — entered · #import:https:::github.com:berriai:litellm post #1986
The left issue spans multiple cross-cutting workflows, identity integrations, notification delivery, security-sensitive credential handling, configuration gating, and UI/API behavior. The right issue is comparatively localized to response-schema propagation in one handler, with focused code changes and tests.
#0 of 0 · 31d18h23m13s ago — current · #import:https:::github.com:berriai:litellm post #2554
The right issue spans authentication policy, key lifecycle behavior, notification delivery, user identity data, and error-handling changes across multiple proxy surfaces, creating substantially more integration and security risk. The left issue is comparatively localized: extending routing configuration and threading per-group values through existing lookup and filtering paths.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search