OCM federation: account states (departed / disabled) across outbound and inbound federated shares #860

Open
opened 2026-10-08 11:28:15 +00:00 by Cordy · 1 comment
Owner

Found during the #857 review (pre-existing; #597 never covered it). Federated (OCM) shares served under /dav/ocm/ (ocm.GrantHandler, cmd/cairnd/main.go ~1253) don't check whether the share's creator is still alive. Public links and internal grants freeze for Departed creators and pause Personal links for Disabled creators (#857), but external pulls through OCM keep working in both cases.

To do:

  • Decide the rule for OCM shares. They're external exposure, so the closest analogue is public links: Departed means frozen; Disabled means paused for Personal content, while Spaces keep serving and get flagged.
  • Apply it at the OCM grant handler, using the same oracle (Status).
  • Show the state in the admin Shares list if OCM shares appear there.
  • Tests per state; update the docs (federation-ocm.md, sharing.md).
Found during the #857 review (pre-existing; #597 never covered it). Federated (OCM) shares served under `/dav/ocm/` (`ocm.GrantHandler`, `cmd/cairnd/main.go` ~1253) don't check whether the share's creator is still alive. Public links and internal grants freeze for **Departed** creators and pause Personal links for **Disabled** creators (#857), but external pulls through OCM keep working in both cases. To do: - Decide the rule for OCM shares. They're external exposure, so the closest analogue is public links: Departed means frozen; Disabled means paused for Personal content, while Spaces keep serving and get flagged. - Apply it at the OCM grant handler, using the same oracle (`Status`). - Show the state in the admin Shares list if OCM shares appear there. - Tests per state; update the docs (federation-ocm.md, sharing.md).
Cordy changed title from OCM outbound grants (/dav/ocm) ignore creator liveness (departed / disabled) to OCM federation: account states (departed / disabled) across outbound and inbound federated shares 2026-10-08 13:00:22 +00:00
Author
Owner

Scope widened (Nikola, 2026-10-08): this now covers OCM federation as a whole, not just the outbound grant handler. To work through when picked up (research first, then decisions):

  • Outbound: shares served to other servers under /dav/ocm/. What happens when the creator is departed or disabled (frozen / paused per #857)?
  • Inbound: shares received from other servers by a local user who then departs or is disabled. Do pending OCM invitations expire? Is anything still served or synced?
  • Admin visibility: do federated shares appear in Administration › Sharing › Shares with the same states, and can they be reviewed?
  • Ending a share at the other side: when a share is frozen or revoked here, does the remote server learn of it? The OCM spec has a share-removal notification.
  • Prior art: how Nextcloud, ownCloud/oCIS and OpenCloud handle federated shares of disabled or deleted users, and what operators reported.

This needs research and decisions before implementation, plus a mockup if admin views change.

**Scope widened (Nikola, 2026-10-08):** this now covers OCM federation as a whole, not just the outbound grant handler. To work through when picked up (research first, then decisions): - **Outbound:** shares served to other servers under `/dav/ocm/`. What happens when the creator is departed or disabled (frozen / paused per #857)? - **Inbound:** shares received from other servers by a local user who then departs or is disabled. Do pending OCM invitations expire? Is anything still served or synced? - **Admin visibility:** do federated shares appear in Administration › Sharing › Shares with the same states, and can they be reviewed? - **Ending a share at the other side:** when a share is frozen or revoked here, does the remote server learn of it? The OCM spec has a share-removal notification. - **Prior art:** how Nextcloud, ownCloud/oCIS and OpenCloud handle federated shares of disabled or deleted users, and what operators reported. This needs research and decisions before implementation, plus a mockup if admin views change.
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#860
No description provided.