Activity: a re-created account sees the old account's history; an ownership transfer does not carry history #981

Closed
opened 2026-10-20 06:33:02 +00:00 by Cordy · 2 comments
Owner

Found in the batch 4 review of #971 (review-e residuals B and C, 2026-10-19). Both predate batch 4 and are not widened by it.

  1. Re-created account. Removing a local account keeps its /home/<user>. A new account with the same name inherits the old home's files, and since #971 its Activity history too, because history is keyed by backend path. The history decision should go with whatever is decided for the files: archive or hide the old account's history when the account is removed, or record an account epoch and hide events older than the new account.
  2. Ownership transfer. When a space or folder changes owner, Activity history stays at the old backend paths. A product choice is needed: should history follow the files to the new owner (with the privacy rules of #971: no third person's events into a new audience), or stay with the old owner?

To do: research how others handle both, then a decision, then tests on posix and s3.

Found in the batch 4 review of #971 (review-e residuals B and C, 2026-10-19). Both predate batch 4 and are not widened by it. 1. **Re-created account.** Removing a local account keeps its `/home/<user>`. A new account with the same name inherits the old home's files, and since #971 its Activity history too, because history is keyed by backend path. The history decision should go with whatever is decided for the files: archive or hide the old account's history when the account is removed, or record an account epoch and hide events older than the new account. 2. **Ownership transfer.** When a space or folder changes owner, Activity history stays at the old backend paths. A product choice is needed: should history follow the files to the new owner (with the privacy rules of #971: no third person's events into a new audience), or stay with the old owner? **To do:** research how others handle both, then a decision, then tests on posix and s3.
Author
Owner

Research and decision (2026-10-28): see the C2 decision sheet.

Background:

  • Microsoft 365 gives a re-created account a new ID and a new OneDrive.
  • A Google transfer keeps the files' history.
  • Nextcloud CVE-2021-32726 (a reused username could take over the new account) is the same class as #838/#851.

Decision (Nikola):

  • A re-created account does not see its predecessor's Activity; administrators still do.
  • Cairn records each directory account's first sign-in and IdP subject to tell them apart; #654 also needs this.
  • On an ownership transfer, history moves with the files, including everyone's events, because the grants are re-pointed by the same transfer.
**Research and decision (2026-10-28):** see the C2 decision sheet. **Background:** - Microsoft 365 gives a re-created account a new ID and a new OneDrive. - A Google transfer keeps the files' history. - Nextcloud CVE-2021-32726 (a reused username could take over the new account) is the same class as #838/#851. **Decision (Nikola):** - A re-created account does not see its predecessor's Activity; administrators still do. - Cairn records each directory account's first sign-in and IdP subject to tell them apart; #654 also needs this. - On an ownership transfer, history moves with the files, including everyone's events, because the grants are re-pointed by the same transfer.
Author
Owner

Shipped in v0.6.366 (PR #1032), both dogfoods bumped.

  • Account start: a re-created account (local delete + create, or a directory account with a new IdP subject under the same provider and identity attribute) and the people it shares with no longer see Activity in its home from before its start. Administrators still do; the audit log keeps everything.
  • New state file first-signins.json (with the data): per username the source (oidc:<issuer>, ldap:<attribute>, local), subject and start. A local record is kept after delete. Changing the LDAP id attribute or the OIDC provider does not start new accounts. Accounts from before the upgrade get no start from their first record.
  • Transfers from a departed owner carry the Activity history to the new owner with everyone's events; if the destination is already shared with others (or the share store can't be read), only the departed and the new owner's events move (WARN line).
  • Rollback: older versions ignore first-signins.json and drop the carried-history stamp.

Backlog: a local record carries its start over to a later directory account of the same name (same class as #654). Live check moved to #1005.

Shipped in v0.6.366 (PR #1032), both dogfoods bumped. - Account start: a re-created account (local delete + create, or a directory account with a new IdP subject under the same provider and identity attribute) and the people it shares with no longer see Activity in its home from before its start. Administrators still do; the audit log keeps everything. - New state file `first-signins.json` (with the data): per username the source (`oidc:<issuer>`, `ldap:<attribute>`, `local`), subject and start. A local record is kept after delete. Changing the LDAP id attribute or the OIDC provider does not start new accounts. Accounts from before the upgrade get no start from their first record. - Transfers from a departed owner carry the Activity history to the new owner with everyone's events; if the destination is already shared with others (or the share store can't be read), only the departed and the new owner's events move (WARN line). - Rollback: older versions ignore `first-signins.json` and drop the carried-history stamp. Backlog: a local record carries its start over to a later directory account of the same name (same class as #654). Live check moved to #1005.
Cordy closed this issue 2026-10-28 01:59:57 +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#981
No description provided.