Take-over on instances without a group listing: no "Take over" action in Administration > Spaces #936

Closed
opened 2026-10-16 00:44:42 +00:00 by Cordy · 3 comments
Owner

Found in the fix-923 fix round (2026-10-16).

What happens: since v0.6.346, on instances without an identity-provider group listing (LDAP-only, local accounts, OIDC without the Keycloak admin client), a session admin can take over a folder that no space claims. This only works through the API (POST /api/v1/spaces with takeOver: true).

  • Administration > Spaces flags no folder as an orphan there. Rows show "Managed by the identity provider" and offer no Take over action.
  • The admin text for a plain create over such a folder says "Take it over from Administration > Spaces", which points at an action those instances don't show.

Options (research first; needs a mockup if the inventory changes):

  • Show unclaimed folders as "Not linked to a space" with a Take over action when there is no listing, with a warning that Cairn cannot tell whether a directory group uses the folder.
  • Or reword the text for these instances and document the API call.
Found in the fix-923 fix round (2026-10-16). **What happens:** since v0.6.346, on instances without an identity-provider group listing (LDAP-only, local accounts, OIDC without the Keycloak admin client), a session admin can take over a folder that no space claims. This only works through the API (`POST /api/v1/spaces` with `takeOver: true`). - Administration > Spaces flags no folder as an orphan there. Rows show "Managed by the identity provider" and offer no Take over action. - The admin text for a plain create over such a folder says "Take it over from Administration > Spaces", which points at an action those instances don't show. **Options (research first; needs a mockup if the inventory changes):** - Show unclaimed folders as "Not linked to a space" with a Take over action when there is no listing, with a warning that Cairn cannot tell whether a directory group uses the folder. - Or reword the text for these instances and document the API call.
Author
Owner

Research done (2026-11-11, scratch/b7e/backlog/research-1137-936.md part B).

Cause: without a group listing, the inventory never marks folders as orphans, so the row reads "Managed by the identity provider" and gets no actions. This is plainly wrong on local-only instances.

Sharper finding: the API take-over ignores the group bindings Cairn keeps. So on instances without a listing, an admin can take over a folder a directory group uses every day, and that group then loses access.

Recommended (option 1b):

  • Refuse take-over of folders bound to a group.
  • Show the other unclaimed folders as "Folder in storage, not linked to a space", with Take over, Assign and Relink and a warning before confirming.
  • Local-only instances get the same label without the warning and without Relink.
  • A new unverified flag, so orphan keeps meaning "verified orphan".

Next: decisions.

**Research done** (2026-11-11, `scratch/b7e/backlog/research-1137-936.md` part B). **Cause:** without a group listing, the inventory never marks folders as orphans, so the row reads "Managed by the identity provider" and gets no actions. This is plainly wrong on local-only instances. **Sharper finding:** the API take-over ignores the group bindings Cairn keeps. So on instances without a listing, an admin can take over a folder a directory group uses every day, and that group then loses access. **Recommended (option 1b):** - Refuse take-over of folders bound to a group. - Show the other unclaimed folders as "Folder in storage, not linked to a space", with Take over, Assign and Relink and a warning before confirming. - Local-only instances get the same label without the warning and without Relink. - A new `unverified` flag, so `orphan` keeps meaning "verified orphan". **Next:** decisions.
Author
Owner

Decisions (2026-11-12): option 1b, as researched.

  • On instances without a listing, Cairn refuses to take over folders bound to a group.
  • Other unclaimed folders show as "Folder in storage, not linked to a space", with Take over, Assign and Relink, and a warning before confirming.
  • Instances with local accounts only: no warning and no Relink.
  • A new unverified flag.

Next: mockups.

**Decisions (2026-11-12):** option 1b, as researched. - On instances without a listing, Cairn refuses to take over folders bound to a group. - Other unclaimed folders show as "Folder in storage, not linked to a space", with Take over, Assign and Relink, and a warning before confirming. - Instances with local accounts only: no warning and no Relink. - A new `unverified` flag. **Next:** mockups.
Author
Owner

Shipped in v0.6.407 (PR #1170), live on both dogfoods.

  • Take over and Assign are refused (409 space-folder-group-bound, audited space-take-over-refused) for a folder bound to a directory group, including a bound record hidden behind an older record of the same name.
  • Without a group listing, folders are shown as "Folder in storage, not linked to a space" (unverified), with a warning in the confirm; Take over always asks first.
  • OIDC without the Keycloak admin client: folders present at start are bound by the #1002 upgrade; the way out ("Leave unbound", then Take over) is in spaces.md.

Docs: spaces.md, groups.md, CHANGELOG.

Shipped in **v0.6.407** (PR #1170), live on both dogfoods. - Take over and Assign are refused (409 `space-folder-group-bound`, audited `space-take-over-refused`) for a folder bound to a directory group, including a bound record hidden behind an older record of the same name. - Without a group listing, folders are shown as "Folder in storage, not linked to a space" (unverified), with a warning in the confirm; Take over always asks first. - OIDC without the Keycloak admin client: folders present at start are bound by the #1002 upgrade; the way out ("Leave unbound", then Take over) is in spaces.md. Docs: spaces.md, groups.md, CHANGELOG.
Cordy closed this issue 2026-11-12 19:12:10 +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#936
No description provided.