Refuse handing files over to a disabled account (transfer and space reassignment) #862

Closed
opened 2026-10-08 13:00:21 +00:00 by Cordy · 0 comments
Owner

Follow-up from #857 (Nikola, 2026-10-08).

Today: transferring a departed owner's files to a disabled account (disabled in AD or Keycloak, so it still exists) is allowed. The files then land with someone who can't sign in.

Decision (Nikola): refuse it, and tell the operator why.

Plan (mockup: transfer-disabled-mockup.html, shown 2026-10-08):

  • The transfer dialog's new-owner picker lists disabled accounts greyed out with a DISABLED tag; they can't be selected. One line explains: "Disabled accounts can't receive a handover. Re-enable the account in the directory first, or choose someone else."
  • Server: POST /api/v1/admin/owners/transfer with a disabled target answers 409 with the message "Handing over to a disabled account is not permitted. Re-enable {name} in the directory first, or choose another owner." The dialog shows that text inline, for the case where the account was disabled after the list loaded.
  • Same rule for Space owner reassignment.
  • Audit: the refusal is recorded.
  • Uses the #857 oracle (Status == Disabled). During an outage the target check uses the last known state; an unseen target counts as not disabled, as in the admin views.
  • Copy and docs: EN/DE/FR/IT, no long dash; update sharing.md and admin-policy.md.

Tests:

  • a disabled target gives 409 with the exact message;
  • an alive target works;
  • a Departed target is refused as before;
  • web test: the disabled option can't be selected and the inline error renders.
Follow-up from #857 (Nikola, 2026-10-08). **Today:** transferring a departed owner's files **to** a disabled account (disabled in AD or Keycloak, so it still exists) is allowed. The files then land with someone who can't sign in. **Decision (Nikola):** refuse it, and tell the operator why. **Plan (mockup: `transfer-disabled-mockup.html`, shown 2026-10-08):** - **The transfer dialog's new-owner picker** lists disabled accounts greyed out with a DISABLED tag; they can't be selected. One line explains: "Disabled accounts can't receive a handover. Re-enable the account in the directory first, or choose someone else." - **Server:** `POST /api/v1/admin/owners/transfer` with a disabled target answers **409** with the message "Handing over to a disabled account is not permitted. Re-enable {name} in the directory first, or choose another owner." The dialog shows that text inline, for the case where the account was disabled after the list loaded. - **Same rule for Space owner reassignment.** - **Audit:** the refusal is recorded. - **Uses the #857 oracle** (`Status == Disabled`). During an outage the target check uses the last known state; an unseen target counts as not disabled, as in the admin views. - **Copy and docs:** EN/DE/FR/IT, no long dash; update sharing.md and admin-policy.md. **Tests:** - a disabled target gives 409 with the exact message; - an alive target works; - a Departed target is refused as before; - web test: the disabled option can't be selected and the inline error renders.
Cordy closed this issue 2026-10-08 18:06:18 +00:00
Sign in to join this conversation.
No labels
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#862
No description provided.