Account liveness per mode: LDAP users resolve; disabled accounts "Paused" (#857) #861

Merged
Cordy merged 17 commits from ldap-857 into main 2026-10-08 11:32:46 +00:00
Owner

Closes #857. v0.6.322.

Spec: docs/superpowers/specs/2026-10-08-ldap-liveness-design.md. Plan: docs/superpowers/plans/2026-10-08-ldap-liveness.md. The mockup was approved.

  • Bug fix (LDAP): in ldap mode every LDAP user read as departed. Their links answered 404, their shares were frozen, and an admin could transfer a live user's home. LDAP users are now checked against the directory, using Recheck from #838 plus a new bounded Ping.
  • Three states: Alive, Disabled and Departed.
    • Disabled means paused: public links into Personal folders stop; links outside a Personal folder, for example in a Space, keep serving with a "Creator disabled" review flag and filter; internal shares keep serving.
    • Disabled is not departed: transfer, revoke and the estate view are refused.
    • The Directory accounts list shows a DISABLED badge.
  • Outage: known names keep their last state and unseen names stay frozen. Transfer, revoke and space reassignment need a fresh Departed answer (503 otherwise).
  • Concurrency: the oracle runs one shared lookup per name on its own 5s context and survives a panic in the lookup. Admin listings warm names with a bounded pass (4 workers, 3s); names that don't answer show neutral there.
  • Docs and CHANGELOG are updated, including the AD read requirement for userAccountControl.

Reviews: each of the 6 tasks was reviewed (with fix rounds). The final whole-branch review led to one fix wave; the re-review says ready to merge.

Verified with Mokapi AD (details on #857): the active user's link works, the disabled user's Personal link is paused, the deleted user's link is frozen and they're the only one listed as departed. Transfer from the disabled user is refused. Known users keep working with the directory stopped.

Follow-up: #860 (OCM grants ignore creator liveness, pre-existing).

Closes #857. v0.6.322. Spec: `docs/superpowers/specs/2026-10-08-ldap-liveness-design.md`. Plan: `docs/superpowers/plans/2026-10-08-ldap-liveness.md`. The mockup was approved. - **Bug fix (LDAP):** in ldap mode every LDAP user read as departed. Their links answered 404, their shares were frozen, and an admin could transfer a live user's home. LDAP users are now checked against the directory, using `Recheck` from #838 plus a new bounded `Ping`. - **Three states:** Alive, **Disabled** and Departed. - Disabled means paused: public links into Personal folders stop; links outside a Personal folder, for example in a Space, keep serving with a "Creator disabled" review flag and filter; internal shares keep serving. - Disabled is not departed: transfer, revoke and the estate view are refused. - The Directory accounts list shows a DISABLED badge. - **Outage:** known names keep their last state and unseen names stay frozen. Transfer, revoke and space reassignment need a fresh Departed answer (503 otherwise). - **Concurrency:** the oracle runs one shared lookup per name on its own 5s context and survives a panic in the lookup. Admin listings warm names with a bounded pass (4 workers, 3s); names that don't answer show neutral there. - **Docs and CHANGELOG** are updated, including the AD read requirement for `userAccountControl`. Reviews: each of the 6 tasks was reviewed (with fix rounds). The final whole-branch review led to one fix wave; the re-review says ready to merge. Verified with Mokapi AD (details on #857): the active user's link works, the disabled user's Personal link is paused, the deleted user's link is frozen and they're the only one listed as departed. Transfer from the disabled user is refused. Known users keep working with the directory stopped. Follow-up: #860 (OCM grants ignore creator liveness, pre-existing).
Cordy merged commit e86b2e737b into main 2026-10-08 11:32:46 +00:00
Cordy deleted branch ldap-857 2026-10-08 11:32:49 +00:00
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#861
No description provided.