What happens to shares when an account is removed? (research + decision) #569
Closed
opened 2026-09-17 01:13:40 +00:00 by Cordy
·
3 comments
No Branch/Tag specified
main
b12v07
b11v07
b10v07
ci-rc-publish
fx15-s3dry
b9v07
b8v07
bench742
b7v07
legal-texts-v0.2
b6v07
b5v07
b4v07
b3v07
sx1139
st742
b2v07
ix1102
fu1098
zp1097
wd1099
tr1100
qf1077
nc1070
ci1
rp1072
lk1073
ab1071
fi1074
si1070
ra1054
wo1056
oc1057
tf1055
sv1063
fg1059
st1058
fs929
mu1039
ls1033
cf975
lf835
dx1023
ml896
a11y2
av1022
r913
r7
r6
r5
r45
r23
r1
b10
b9
fix-b5
fix-b4
fix-b3
fix-b2
fix-b1
fix-922
fix-923
fix-911
fix-343b
batch-a
v0.6.413
v0.6.412
v0.6.411
v0.6.410
v0.6.409
v0.6.408
v0.6.407
v0.6.406
v0.6.405
v0.6.404
v0.6.403
v0.6.402
v0.6.401
v0.6.400
v0.6.399
v0.6.398
v0.6.397
v0.6.396
v0.6.395
v0.6.394
v0.6.393
v0.6.392
v0.6.391
v0.6.390
v0.6.389
v0.6.388
v0.6.387
v0.6.386
v0.6.385
v0.6.384
v0.6.383
v0.6.382
v0.6.381
v0.6.380
v0.6.379
v0.6.378
v0.6.377
v0.6.376
v0.6.375
v0.6.374
v0.6.373
v0.6.372
v0.6.371
v0.6.370
v0.6.369
v0.6.368
v0.6.367
v0.6.366
v0.6.365
v0.6.364
v0.6.363
v0.6.362
v0.6.361
v0.6.360
v0.6.359
v0.6.358
v0.6.357
v0.6.356
v0.6.355
v0.6.354
v0.6.353
v0.6.352
v0.6.351
v0.6.350
v0.6.349
v0.6.348
v0.6.347
v0.6.346
v0.6.345
v0.6.344
v0.6.343
v0.6.342
v0.6.341
v0.6.340
v0.6.339
v0.6.338
v0.6.337
v0.6.336
v0.6.335
v0.6.334
v0.6.333
v0.6.332
v0.6.331
v0.6.330
v0.6.329
v0.6.328
v0.6.327
v0.6.326
v0.6.325
v0.6.324
v0.6.323
v0.6.322
v0.6.321
v0.6.320
v0.6.319
v0.6.318
v0.6.317
v0.6.316
v0.6.315
v0.6.314
v0.6.313
v0.6.312
v0.6.311
v0.6.310
v0.6.309
v0.6.308
v0.6.307
v0.6.306
v0.6.305
v0.6.304
v0.6.303
v0.6.302
v0.6.301
v0.6.300
v0.6.299
v0.6.298
v0.6.297
v0.6.296
v0.6.295
v0.6.294
v0.6.293
v0.6.292
v0.6.291
v0.6.290
v0.6.289
v0.6.288
v0.6.287
v0.6.286
v0.6.285
v0.6.284
v0.6.283
v0.6.282
v0.6.281
v0.6.280
v0.6.279
v0.6.278
v0.6.277
v0.6.276
v0.6.275
v0.6.274
v0.6.273
v0.6.272
v0.6.271
v0.6.270
v0.6.269
v0.6.268
v0.6.267
v0.6.266
v0.6.265
v0.6.264
v0.6.263
v0.6.262
v0.6.261
v0.6.260
v0.6.259
v0.6.258
v0.6.257
v0.6.256
v0.6.255
v0.6.254
v0.6.253
v0.6.252
v0.6.251
v0.6.250
v0.6.249
v0.6.248
v0.6.247
v0.6.246
v0.6.245
v0.6.244
v0.6.243
v0.6.242
v0.6.241
v0.6.240
v0.6.239
v0.6.238
v0.6.237
v0.6.236
v0.6.235
v0.6.234
v0.6.233
v0.6.232
v0.6.231
v0.6.230
v0.6.229
v0.6.228
v0.6.227
v0.6.226
v0.6.225
v0.6.224
v0.6.223
v0.6.222
v0.6.221
v0.6.220
v0.6.219
v0.6.218
v0.6.217
v0.6.216
v0.6.215
v0.6.214
v0.6.213
v0.6.212
v0.6.211
v0.6.210
v0.6.209
v0.6.208
v0.6.207
v0.6.206
v0.6.205
v0.6.204
v0.6.203
v0.6.202
v0.6.201
v0.6.200
v0.6.199
v0.6.198
v0.6.197
v0.6.196
v0.6.195
v0.6.194
v0.6.193
v0.6.192
v0.6.191
v0.6.190
v0.6.189
v0.6.188
v0.6.187
v0.6.186
v0.6.185
v0.6.184
v0.6.183
v0.6.182
v0.6.181
v0.6.180
v0.6.179
v0.6.178
v0.6.177
v0.6.176
v0.6.175
v0.6.174
v0.6.173
v0.6.172
v0.6.171
v0.6.170
v0.6.169
v0.6.168
v0.6.167
v0.6.166
v0.6.165
v0.6.164
v0.6.163
v0.6.162
v0.6.161
v0.6.160
v0.6.159
v0.6.158
v0.6.157
v0.6.156
v0.6.155
v0.6.154
v0.6.153
v0.6.152
v0.6.151
v0.6.150
v0.6.149
v0.6.148
v0.6.147
v0.6.146
v0.6.145
v0.6.144
v0.6.143
v0.6.142
v0.6.141
v0.6.140
v0.6.139
v0.6.138
v0.6.137
v0.6.136
v0.6.135
v0.6.134
v0.6.133
v0.6.132
v0.6.131
v0.6.130
v0.6.129
v0.6.128
v0.6.127
v0.6.126
v0.6.125
v0.6.124
v0.6.123
v0.6.122
v0.6.121
v0.6.120
v0.6.119
v0.6.118
v0.6.117
v0.6.116
v0.6.115
v0.6.114
v0.6.113
v0.6.112
v0.6.111
v0.6.110
v0.6.109
v0.6.108
v0.6.107
v0.6.106
v0.6.105
v0.6.104
v0.6.103
v0.6.102
v0.6.101
v0.6.100
v0.6.99
v0.6.98
v0.6.97
v0.6.96
v0.6.95
v0.6.94
v0.6.93
v0.6.92
v0.6.91
v0.6.90
v0.6.89
v0.6.88
v0.6.87
v0.6.86
v0.6.85
v0.6.84
v0.6.83
v0.6.82
v0.6.81
v0.6.80
v0.6.79
v0.6.78
v0.6.77
v0.6.76
v0.6.75
v0.6.74
v0.6.73
v0.6.72
v0.6.71
v0.6.70
v0.6.69
v0.6.68
v0.6.67
v0.6.66
v0.6.65
v0.6.64
v0.6.63
v0.6.62
v0.6.61
v0.6.60
v0.6.59
v0.6.58
v0.6.57
v0.6.56
v0.6.55
v0.6.54
v0.6.53
v0.6.52
v0.6.51
v0.6.50
v0.6.49
v0.6.48
v0.6.47
v0.6.46
v0.6.45
v0.6.44
v0.6.43
v0.6.42
v0.6.41
v0.6.40
v0.6.39
v0.6.38
v0.6.37
v0.6.36
v0.6.35
v0.6.34
v0.6.33
v0.6.32
v0.6.31
v0.6.30
v0.6.29
v0.6.28
v0.6.25
v0.6.24
v0.6.23
v0.6.22
v0.6.21
v0.6.20
v0.6.19
v0.6.18
v0.6.17
v0.6.16
v0.6.15
v0.6.14
v0.6.12
v0.6.11
v0.6.10
v0.6.9
v0.6.8
v0.6.7
v0.6.6
v0.6.5
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.7
v0.5.6
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
v0.4.12
v0.4.11
v0.4.10
v0.4.9
v0.4.8
v0.4.7
v0.4.6
v0.4.5
v0.4.4
v0.4.3
v0.4.2
v0.4.1
v0.3.30
v0.3.29
v0.3.28
v0.3.27
v0.3.26
v0.3.25
v0.3.24
v0.3.23
v0.3.22
v0.3.21
v0.3.20
v0.3.19
v0.3.18
v0.3.17
v0.3.16
v0.3.15
v0.3.14
v0.3.13
v0.3.12
v0.3.11
v0.3.10
v0.3.9
v0.3.8
v0.3.7
v0.3.6
v0.3.5
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.0.3
v0.0.2
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#569
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Split out of #529's mockup review (2026-09-17). Nikola: "for now we have 'an admin can see them' in place, but the instinct to get a decision on this is right."
The question
When an account is removed — a local account deleted, or a directory account that stops existing — what happens to the shares that account created?
Once #529 gives
share.Storean addressee, every share has two identities that can disappear: the creator and the addressee. The failure modes are different and both need an answer:CreatedBydanglesThe addressee half is settled. This issue is about the creator half, which is not.
What Cairn does today
Nothing deliberate.
share.SharecarriesCreatedByas a string;Store.List(ctx, createdBy)filters by it. Removing the account does not touch the shares. So the shares keep working, owned by a name that no longer resolves, and the only way to find them is an admin listing.That is accidentally the fail-closed-ish answer, but it was never chosen, and it has a sharp edge worth naming: a public link created by a departed employee keeps serving their files. Nobody is notified, nothing expires, and the file is still readable by anyone holding the URL. For a product whose pitch is that the instance admin is accountable for what is on their own hardware, that is the wrong default to arrive at by omission.
There is a second-order problem specific to Cairn: after #529, a read goes through the owner's key scope. If the owner is gone, whose scope opens the file? The recovery identity presumably — but that path needs to be deliberate, not incidental, and it interacts with key custody (#528) and the retained-key rotation story.
Deep research task
Use Superpowers. Compare ownCloud, oCIS, Nextcloud and Seafile:
Then propose options with a recommendation, the way #529's crypto question was handled: state the constraint first, lay out the two or three real choices, recommend one, and name the consequence that has to be said out loud rather than buried.
Scope
Research and a recorded decision. Implementation is a follow-up once the decision exists — it may well be small (an admin listing plus a defined rule), but the rule has to be chosen before it is coded.
Blocked by nothing. Wants to be settled before the closed beta, since the first real user deletion will otherwise settle it by accident.
Research done — four products, two failure families, options + recommendation below
1. What each product actually does on user deletion
Nextcloud — deleting a user deletes their files and every share they created, public links included. The escape hatch is
occ files:transfer-ownership, run manually before deletion; it moves files plus outgoing shares into a subfolder of the target user. Trash is not transferred, incoming shares are not moved by default. There is no automatic step, no warning in the deletion flow, and admins who deleted first and read the manual second show up in the forums asking how to restore from backup.ownCloud classic — same model; the admin manual warns outright that deleting a user destroys everything they shared. There is a
cleanup-orphaned-sharesmaintenance command, which tells you orphans happen often enough to need a broom.oCIS — the opposite failure: deletion orphans content instead of destroying it. A deleted user's personal and project spaces keep existing (#4195), the admin cannot access or delete them (#4194, #4196), and removing a space's only Manager leaves the space unmanageable by anyone including admins (#4105, #7265). Undead data nobody controls — on the product whose whole redesign was supposed to fix this class.
Seafile — library-centric: deleting a library cancels all shares in it (restorable from admin trash); user deletion is handled by admins transferring libraries, with its own bug tail — ownership transfer drops assigned user/group permissions (forum 16706), transferring groups from a deleted user misbehaves (forum 14484).
2. The pitfalls they hit
The transfer tool is where Nextcloud bleeds: public shares silently deleted on transfer (#60223, root cause a cascade-delete via the
parentcolumn, fixed only in #64209 — this September); "share points at deleted file, skipping" losing shares mid-transfer (#25693); silent failure on insufficient target quota (#31868); files invisible in the web UI after transfer on object storage (#48463). Beyond the tool: deleting a shared file leaves orphaned link rows serving an error page (#46369), and NC18 once cascade-wiped the wholeoc_sharetable off one federated-share removal (forum).3. What users say
The recurring thread shape is "we migrated auth / offboarded someone / cleaned up accounts, and the shares vanished" — e.g. deleted users and shared links are gone, recover from backup? (local→AD migration deleted every share those users had made). Nobody is warned at deletion time; discovery is downstream, by the people the shares were serving.
4. What this means for Cairn
Two failure families to avoid: cascade surprise (Nextcloud/ownCloud — deletion silently destroys shares, sometimes other people's) and undead orphans (oCIS — content survives that nobody, admin included, can govern). Both stem from the same omission: no preview, no deliberate rule, no notification.
Cairn has one constraint none of them have, and it decides half the question for us: reads resolve through the owner's key scope. On
keycloak-profilecustody, a vanished directory account takes its key with it — a departed owner's grants and strong links cannot keep serving through the normal path, only through a deliberate recovery-identity code path. So "keep everything working like nothing happened" is not a lazy default available to us; it would have to be built on purpose. Good.Options
A — Freeze, surface, decide (recommended). When the creator no longer resolves — deleted locally or vanished from the directory — everything they created stops serving: grants stop resolving (already the fail-closed rule for addressees; apply it to creators symmetrically) and public links answer 404 exactly like an expired link. Nothing is mutated; files stay where they are. The admin gets a Departed owners listing (shares grouped by dangling
CreatedBy) with per-share revoke and, if the content must stay shared, the admin re-shares it from an account that exists — an explicit, audited act by an accountable person, not a silent transfer. Local deletion gets a confirmation dialog listing what will stop serving (the preview every competitor lacks).B — Cascade revoke on local deletion + freeze for directory accounts. Deliberate delete-time revocation (audited) for local accounts, freeze for IdP vanishing (which has no deletion event to hook). Two rules where A has one; the split invites the Nextcloud class of surprise on the local path, and the end state is the same bytes-wise. Only worth it if "deleted = record gone" matters more than a uniform rule.
C — Transfer-ownership tooling. The competitors' answer, with their documented bug tail, and in Cairn a transfer is a cross-scope move, which re-encrypts — colliding with holds (#138-class), versions (#541) and quota. Not for v0.7; if real demand appears, build it later on top of A, as an explicit admin action.
The consequence said out loud, per the brief: under A, the day someone leaves, their public links die. That is the point — a departed employee's files should not keep flowing outward under nobody's accountability — but it will surprise whoever was consuming the link, so the handbook states it and the Departed-owners panel makes the re-share one click for the admin. The alternative (links that keep serving via the recovery key) means the server routinely decrypts with the break-glass identity — a much worse sentence to have to write down.
Implementation size if A is chosen: small, as the issue hoped — a creator-liveness check where grants resolve and where
/s/serves (needs a "known principals" oracle: local store + seats seen-list + live IdP answer, fail-frozen on IdP outage so an outage doesn't mass-kill links — freeze is temporary and self-heals when the directory returns); the Departed-owners admin listing; the local-delete confirmation preview; audit verbs; handbook sentences. Interacts cleanly with #595 (same governance neighborhood) and gives #569's addressee half its mirror.Your call — A, B, or C (or A with amendments).
Decision (Nikola, 2026-09-18): Option A as the automatic rule, plus Option C built deliberately on top of it — from the start, not later.
Rationale, in his words: transfer tooling is already a market demand (every competitor's admins reach for it, and Nextcloud only just fixed its worst transfer bug); "showing up to a market with the solution in hand already is better than showing up with a marginally better solution."
So the shipped behaviour will be:
Cairn-specific design lines for the transfer, so we do not import Nextcloud's bug tail:
encrypt/group.go), already refuse under legal hold, already hit quota and audit. A transfer is "move/home/<gone>/…into/home/<target>/…" plus rewriting the affected share records — not a parallel copy machine.CreatedBybecomes the target admin-chosen owner, addressees untouched. Fail loudly on any record that cannot be re-pointed; never skip-and-continue (the "share points at deleted file, skipping" lesson).Implementation issue follows with the full brief; the Departed-owners panel and the transfer flow get a mockup before any UI is built.
Closing: this issue's scope (research + recorded decision) is complete — Option A (freeze + surface) with C (transfer) built on top, decided 2026-09-18 above — and the implementation shipped and closed as #597. Live UI verification of the departed-owner flow is pending as a dogfood exercise (delete one of the sharer1/sharer2 test accounts, confirm the frozen rows, Departed-owners listing, delete preview and transfer); any findings there get filed as fresh issues against the shipped behaviour.
Cordy referenced this issue2026-09-23 01:02:07 +00:00