Read-only space membership (viewer role via IdP group) #64
Loading…
Add table
Add a link
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?
Derived from the public-sector analysis (#59, docs/PUBLIC-SECTOR.md). Auditor/internal-affairs persona: must read everything in a space, change nothing. Today every space member can write.
Design (follows the directory-is-the-source-of-truth philosophy — no parallel permission system):
<space>-rogrants read-only access to/spaces/<space>(suffix configurable, e.g.auth.spaceReadOnlySuffix, default-ro).internal/storage/scope) so web UI, REST, WebDAV, and TUS behave identically: reads/lists succeed, any mutation → 403./spaceslisting includes read-only spaces (with a viewer indicator).Acceptance: user only in
case-x-rocan list/download in/spaces/case-xbut PUT/DELETE/MKCOL fail with 403 across web + WebDAV; adding them tocase-xin the IdP grants write at next sign-in with no Cairn-side change.