Editor saves and space owners: open rulings from v0.6.345 (413 for oversize, 403 token burn, power-mode owners) #921

Open
opened 2026-10-15 20:59:43 +00:00 by Cordy · 1 comment
Owner

Rulings made during fix-911 (v0.6.345) that need research and a decision.

  1. Editor save over the per-file limit (maxFileBytes).
    • Today: the save answers 507 quota-exceeded with no size hint, so Collabora shows a conflict or reloads as before.
    • Option: answer 413, which Collabora shows as read-only for the session, with one message.
  2. Held or read-only refusal during an editing session.
    • Today: the save answers 403, and Collabora treats that as an expired token. After 3 tries the session can never save again.
    • Decide: whether these refusals should answer differently (423, or 503 with the size hint) so the edits stay recoverable.
  3. Owners of IdP-managed spaces (power mode). They currently get no "permanently delete anything" right in Deleted files; only Cairn-created spaces have an owner role (R4). Checking would cost a Keycloak admin call per decision, so it needs a cached check.

Research first; see scratch/b7e/batch907/913-research.md and 911-research.md.

Rulings made during fix-911 (v0.6.345) that need research and a decision. 1. **Editor save over the per-file limit (`maxFileBytes`).** - **Today:** the save answers 507 `quota-exceeded` with no size hint, so Collabora shows a conflict or reloads as before. - **Option:** answer 413, which Collabora shows as read-only for the session, with one message. 2. **Held or read-only refusal during an editing session.** - **Today:** the save answers 403, and Collabora treats that as an expired token. After 3 tries the session can never save again. - **Decide:** whether these refusals should answer differently (423, or 503 with the size hint) so the edits stay recoverable. 3. **Owners of IdP-managed spaces (power mode).** They currently get no "permanently delete anything" right in Deleted files; only Cairn-created spaces have an owner role (R4). Checking would cost a Keycloak admin call per decision, so it needs a cached check. Research first; see `scratch/b7e/batch907/913-research.md` and `911-research.md`.
Author
Owner

Addition from fix-923 Task 3 (2026-10-16): in power mode, the /meta former-name rule (D8: former names are shown to the owner and admins only) checks the stored space owner. An owner recorded only in the identity provider who asks by a former name gets that former name back, not the current one. This is the same root cause as item 3 here (power-mode owners), so the fix should cover both.

**Addition from fix-923 Task 3 (2026-10-16):** in power mode, the `/meta` former-name rule (D8: former names are shown to the owner and admins only) checks the stored space owner. An owner recorded only in the identity provider who asks by a former name gets that former name back, not the current one. This is the same root cause as item 3 here (power-mode owners), so the fix should cover both.
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#921
No description provided.