v0.6.352: deployment, directory, TLS (#752 Kubernetes and configuration, #741 Active Directory / LDAP / Entra, #740 TLS and private CAs) #986

Merged
Cordy merged 51 commits from fix-b5 into main 2026-10-24 14:20:50 +00:00
Owner

Batch 5. The decisions on #740, #741 and #752 were made on 2026-10-24.

#740, TLS and private CAs:

  • tls.caDir / CAIRN_CA_DIR adds trusted CAs on top of the public ones for every outbound client, through one shared helper. It is re-read without a restart.
  • Optional native TLS via tls.certDir / CAIRN_TLS_DIR. Renewed certificates are picked up without a restart, the server sends HSTS, and peering gRPC works over TLS.
  • tls.minVersion applies to the listener only.
  • There is no insecure fallback, and a broken configured certificate refuses the start.
  • The crypto client never uses a proxy.
  • The Dockerfile has a CA bundle and a matching Go builder.

#741, Active Directory, LDAP and Entra:

  • New settings: ldapDirectoryType, ldapAllowedGroups, ldapGroupBaseDn, ldapNestedGroups, ldapLoginAttrs, failover across several URLs, and ldapAllowPlain.
  • Removal from an allowed group is treated as disabled at the next re-check: sessions end, app passwords are paused, and the mass-miss guard applies.
  • oidcAllowedGroups matches by name or full path.
  • Bugs fixed:
    • the re-check skipped the filter;
    • StartTLS had no server name;
    • only the first %s was replaced;
    • groups were accepted from any OU;
    • group checks ran before the password bind.

#752, Kubernetes and configuration:

  • A CAIRN_X_FILE form for every secret.
  • A misspelled config key refuses the start.
  • example.config.json boots as shipped.
  • New settings reference page, with a drift test.
  • Chart 0.5.0:
    • meets the restricted Pod Security standard;
    • adds env, envFrom and extra volumes, plus trust and TLS inputs;
    • fixes the selector bug without a Deployment selector change;
    • makes image.repository required.

Docs:

  • New: deploy-kubernetes.md, configuration-reference.md, directory-ldap-ad.md, directory-entra-id.md, tls-certificates.md.
  • Edits across the handbook, plus the CHANGELOG with upgrade and rollback notes.

Process: three research files, Tasks A, B and C with reviews and fix rounds, a docs task, a final whole-branch review and a final fix round. Every package passes, -race on the batch-5 packages, go vet, gofmt and the web checks; no U+2014. The trail is in .superpowers/sdd/2026-10-24-batch5/. The UI pieces (Certificates card, LDAP facts, login messages) follow in #985.

Batch 5. The decisions on #740, #741 and #752 were made on 2026-10-24. **#740, TLS and private CAs:** - `tls.caDir` / `CAIRN_CA_DIR` adds trusted CAs on top of the public ones for every outbound client, through one shared helper. It is re-read without a restart. - Optional native TLS via `tls.certDir` / `CAIRN_TLS_DIR`. Renewed certificates are picked up without a restart, the server sends HSTS, and peering gRPC works over TLS. - `tls.minVersion` applies to the listener only. - There is no insecure fallback, and a broken configured certificate refuses the start. - The crypto client never uses a proxy. - The Dockerfile has a CA bundle and a matching Go builder. **#741, Active Directory, LDAP and Entra:** - New settings: `ldapDirectoryType`, `ldapAllowedGroups`, `ldapGroupBaseDn`, `ldapNestedGroups`, `ldapLoginAttrs`, failover across several URLs, and `ldapAllowPlain`. - Removal from an allowed group is treated as disabled at the next re-check: sessions end, app passwords are paused, and the mass-miss guard applies. - `oidcAllowedGroups` matches by name or full path. - Bugs fixed: - the re-check skipped the filter; - StartTLS had no server name; - only the first `%s` was replaced; - groups were accepted from any OU; - group checks ran before the password bind. **#752, Kubernetes and configuration:** - A `CAIRN_X_FILE` form for every secret. - A misspelled config key refuses the start. - `example.config.json` boots as shipped. - New settings reference page, with a drift test. - Chart 0.5.0: - meets the restricted Pod Security standard; - adds `env`, `envFrom` and extra volumes, plus trust and TLS inputs; - fixes the selector bug without a Deployment selector change; - makes `image.repository` required. **Docs:** - New: `deploy-kubernetes.md`, `configuration-reference.md`, `directory-ldap-ad.md`, `directory-entra-id.md`, `tls-certificates.md`. - Edits across the handbook, plus the CHANGELOG with upgrade and rollback notes. **Process:** three research files, Tasks A, B and C with reviews and fix rounds, a docs task, a final whole-branch review and a final fix round. Every package passes, `-race` on the batch-5 packages, `go vet`, gofmt and the web checks; no U+2014. The trail is in `.superpowers/sdd/2026-10-24-batch5/`. The UI pieces (Certificates card, LDAP facts, login messages) follow in #985.
Existing ldapauth test fixtures dial a fake plain ldap:// directory: they
now set AllowPlain (TestNewValidation uses ldaps://), because New refuses
plain transport by default.
resolve_test.go's fake directory gains the notAllowed field so tests can
return DirStatus.NotAllowed.
- every re-check checks the entry against the user filter (login-name
  clauses become presence tests) and the allowed groups; failing them is
  DirStatus.NotAllowed (handled like disabled)
- with ldapGroupBaseDn only groups under it count (spaces, adminGroups,
  allowed groups), named by sAMAccountName, else cn; nested through
  LDAP_MATCHING_RULE_IN_CHAIN when ldapNestedGroups (default for ad)
- without ldapGroupBaseDn a start WARN says groups from any OU count
- an allowed-group name that matches no group or several, or an
  unreadable group DN, is a configuration fault (outage), never a verdict
- accountExpires in the past refuses sign-in and reads as disabled
- ldapUserFilter and ldapLoginAttrs together, an unparsable filter, or a
  %s under a NOT refuse start
The mass-miss WARN now also names removal from the allowed groups.
New handbook pages: deploy-kubernetes.md, directory-ldap-ad.md,
directory-entra-id.md, tls-certificates.md; configuration-reference.md
polished (where it lives, when it applies, precedence, _FILE rules,
unknown-key refusal, where files live). Updates to deployment.md,
local-accounts.md, users-access.md, peering.md, encryption.md,
document-editing.md, updates.md, security-standards.md, index.md,
README.md, ARCHITECTURE.md (tlstrust seam, config strictness), the
values.yaml and compose comments. CHANGELOG v0.6.352 and chart
appVersion v0.6.352.
Cordy merged commit 07602d028f into main 2026-10-24 14:20:50 +00:00
Author
Owner

Released v0.6.352 (2026-10-24). It is merged and tagged, and the image is built. Both dogfoods are bumped (homelab-config 6ef66ad) and start cleanly:

  • Config check: the strict key check passed on both real configs, so neither has unknown keys.
  • Outbound TLS: both log tls: no tls.caDir set; outbound TLS trusts the system CA bundle only and come up with tls=false. Every outbound integration that runs at start still works through the new shared trust: OIDC discovery, the OpenBao custody self-check, S3/Garage, the converter and Collabora.

CI note: the first PR run failed in the real helm lint. The Chart.yaml description had become a plain YAML scalar containing : . It is fixed by quoting it, and a test now catches unquoted : values, which the sandbox's stand-in renderer could not see.

Still open:

  • Nikola signs in on both instances to confirm the OIDC token exchange through the new client.
  • LDAP/AD, native TLS and _FILE are not used on either dogfood, so they are covered by tests only. A check against a real AD (Manuel's environment) is recommended.
**Released v0.6.352 (2026-10-24).** It is merged and tagged, and the image is built. Both dogfoods are bumped (homelab-config 6ef66ad) and start cleanly: - **Config check:** the strict key check passed on both real configs, so neither has unknown keys. - **Outbound TLS:** both log `tls: no tls.caDir set; outbound TLS trusts the system CA bundle only` and come up with `tls=false`. Every outbound integration that runs at start still works through the new shared trust: OIDC discovery, the OpenBao custody self-check, S3/Garage, the converter and Collabora. **CI note:** the first PR run failed in the real `helm lint`. The Chart.yaml description had become a plain YAML scalar containing `: `. It is fixed by quoting it, and a test now catches unquoted `: ` values, which the sandbox's stand-in renderer could not see. Still open: - Nikola signs in on both instances to confirm the OIDC token exchange through the new client. - LDAP/AD, native TLS and `_FILE` are not used on either dogfood, so they are covered by tests only. A check against a real AD (Manuel's environment) is recommended.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#986
No description provided.