Repository navigation
LiteGate v2.15.1
Highlights
- Unified assignments: Hierarchy members'
userIdsaccept emails/exact IDs alongsidessoGroups, resolving compatible paths with inherited memberships and key allowances. Local users retain explicit ID assignments. - Verification fix:
generic_require_verified_email/ Helmconfig.genericRequireVerifiedEmailconsistently governs explicitly false generic SSO claims. Missing claims and OIDC behavior are unchanged; hierarchy matching does not override verification policy. - Identity: New users remain config-only until authenticated subject provisioning, without generating a key or pre-login placeholder.
Release Artifacts
| Artifact | Get it |
|---|---|
| Docker image | docker pull ghcr.io/brtydse100/litegate:2.15.1GHCR |
| Live demo | Current demo |
| Docs | Versioned documentation |
| Source | Source |
| License | MIT license |
Upgrade Notes
- Breaking: Nonempty standalone email-mapping options from v2.15.0 now fail startup. Upgrade chart/image together.
- Remove
organization_mapping,organization_mapping_file,ORGANIZATION_MAPPING,ORGANIZATION_MAPPING_FILE, Helmconfig.organizationMapping/config.organizationMappingFile, and mounts used only for the old mapping. - Move emails into
organizationHierarchy.levels[].groups[].members[].userIds; keepssoGroupson the same member. Exact IDs, parent inheritance and budgets remain supported. - Preserve SQLite. Canonical provider/subject bindings remain valid; unbound reservations need durable ownership evidence and pending candidates need their authenticated existing subject. No new reservations, deletions or key transfers. Existing keys/spend/memberships remain; revocation is an operator decision.
Changes: #40 by @brtydse100.
Full Changelog: v2.15.0...v2.15.1
Contributors
Thanks to @brtydse100 for the changes in this release.