ocm: Nextcloud/ownCloud trusted-servers compat with per-server derived directory (#455) #479
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-455"
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?
Implements the locked #455 decisions per the approved rev-2 mockups (ocm-directory-rev2, ocm-status-servers-rev2).
Backend (TDD, red witnessed on the runner):
internal/ocm/directory.go:status.php(JSON with a ≥9.0 version, active only while a legacy-dialect server is allow-listed), OCSrequest-shared-secret(allow-list gated, async callback with trailing-slash retry — the classic NC forum mismatch) andget-shared-secret(always 403: Cairn never initiates), CardDAV sync surface atremote.php/dav/addressbooks/system/system/system(REPORT sync-collection with per-server sync tokens + 404 tombstones via a cumulative Gone list, per-user vCards withCLOUD:address, Basic auth where only the per-server secret identifies).optoutbeats everything, thenoptin) → contact → sent → accepted (a merely received share never lists anyone).DirSubsetenumerates only users present in our own state — no IdP enumeration ever.GET/POST /api/v1/ocm/directory(user rows + per-server override, audited asocm-directory-override),GET /api/v1/admin/ocm/directory(visibility only)./admin/ocm/statusgainslegacyServers.Frontend: Directory tab (visibility-only table + explanatory foot), "Where you appear" card in Federated → Contacts (derivation always named, one link per row overrides either way), Status tab compat row, legacy product sub-line, sharpened legacy Remove confirm. i18n ×4.
Docs: handbook "Appearing in Nextcloud and ownCloud Trusted servers" (incl. no-trailing-slash note and the server-wall granularity), CHANGELOG v0.6.158.
Closes #455.