Unverified50% confidenceDecision RuleExact time
When rotating the master key in LiteLLM, if there is no salt key, use POST /key/regenerate with new_master_key (back up the database first); if there is a salt key, do not call that endpoint, just replace the key and restart.
1
Sources
50%
Confidence
Long-term
Relevance
10/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedPasskeys are not always exportable by design, and some passkeys may need to be re-registered in new tools during migration.69% similarUnverifiedv0.10.1 added the ragleap key --rotate command: it generates a new random API Key and writes it to .env, restarts only the application container, verifies that the old Key is rejected and the new Key works, then prints the new link, without touching the database at all.62% similarUnverifiedDuring key rotation, the JWKS endpoint publishes both the new and old public keys simultaneously (distinguished by different kids), allowing verifiers to still validate existing tokens issued with the old key during the transition period.60% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1017243API
curl https://kongchang.com/api/v1/knowledge/claims/1017243MCP
get_claim(id=1017243)