Repository navigation
LiteGate v2.15.4
Artifacts
| Artifact | Get it |
|---|---|
| Docker image | docker pull ghcr.io/brtydse100/litegate:2.15.4GHCR |
| Live demo | Current demo |
| Docs | Versioned documentation |
| Source | Source |
| License | MIT license |
What's Changed
- Migrate existing hierarchy users at startup and preserve stored key lookup by @brtydse100 in #43
Stored keys and startup hierarchy
Owned-key lists retain their original identifiers when refreshed LiteLLM metadata
contains null, masked or replaced identifier fields. Existing stored secrets
remain available with the same SQLite volume and owner; ownership checks remain
unchanged. The personal page waits for configuration and key lookup results
before suggesting replacement. This reproduces an identifier-overwrite failure;
it does not establish the cause of a particular deployed incident.
Startup awaits its first hierarchy reconciliation attempt, then retries every
60 seconds. Exact-ID lookup takes precedence. Unresolved email selectors search
all relevant pages and require one normalized exact existing account, re-read by
actual ID before assignment. Missing users are skipped; no accounts or keys are
created, deleted or rotated by discovery. Keys retain secrets, aliases, models
and spend through existing policy migration.
Identity and operational limits
Remote-derived email assignments are operator policy, not SSO identity proof.
Every pass revalidates them; changed/ambiguous/incomplete results, local/admin
matches and path conflicts skip writes with errors. Verified accepted/rejected
claims, subject login, email verification and stored-secret ownership remain
unchanged. No new dependencies, services, tables or backend settings are required.
Keep the SQLite volume. Each scan allows 100 pages of 100 users and 60 seconds,
with five concurrent lookups. Per-user failures retry; initial completion does
not promise all remote writes succeeded. Helm allows 30 minutes for startup;
large installations may need longer.
Full Changelog: v2.15.3...v2.15.4
Contributors
Thanks to @brtydse100 for the changes in this release.