Skip to content

integrations/ocm/: receive Open Cloud Mesh shares (phase 2) #138

Open

Description

@michielbdejong

Repo: ontola/atomic-plugins. Base branch: main.
Design: docs/design/server-plugin-routes.md (atomic-plugins PR #108, for atomic-plugins#88), sections 3, 4 (phase 2).
Depends on: ontola/atomic-server#1716 (the ocm discovery claim), ontola/atomic-server#1717, ontola/atomic-server#1718, #134.
Needs --plugin-routes read-write.

Scope

Discovery, shares, notifications and invite-accepted; received shares
listed in a drive table. Evidence: a share from a Nextcloud peer.

From the design in #108 (docs/design/server-plugin-routes.md, #88). Filed by the atomic-plugins oversight session.

Activity

  1. michielbdejong commented on Sep 25, 2026

    @michielbdejong
    ContributorAuthor

    Per Michiel's decision, the server-protocol plugins are owned by the Codex PRs; this is covered by #159 (OCM). The atomic-plugins oversight session won't implement it separately.

  2. michielbdejong commented on Sep 29, 2026

    @michielbdejong
    ContributorAuthor

    #218 merged: the Open Cloud Mesh plugin receives OCM 1.5 file shares. The key is found through the sender's JWKS; the file is fetched into the blob store via fetches; SHARE_ACCEPTED is sent back; SHARE_UNSHARED and permission-change notifications are handled. The real-host e2e passes at pin candidate16 against a local OCM peer. Not done yet: sending shares, WebDAV serving and token exchange.

  3. michielbdejong commented on Oct 1, 2026

    @michielbdejong
    ContributorAuthor

    Real-peer spike done (PR #256). Nextcloud 35.0.1 (official Docker image) was tested against the plugin on the open-cloud-mesh lane's server, all on loopback.

    What Nextcloud sends:

    • RFC 9421 tag="ocm" signatures with an ES256 key from its JWKS.
    • The legacy webdav/options share protocol, with no uri. The file is at /public.php/webdav/ with Basic <secret>:.
    • shareWith written as bob@http(s)://host.
    • Folders sent as resourceType: file.
    • SHARE_UNSHARED without senderDomain.

    At the pin, every Nextcloud share is refused with 401, because the host doesn't accept EC JWKs.

    Fixes:

    With both, the opt-in e2e/nextcloud.spec.ts (OCM_NEXTCLOUD_E2E=1) passes. A real Nextcloud share arrives as a File, unsharing marks it unshared, and a folder is refused.

    Remaining:


    Generated by Claude Code

  4. added a commit that references this issue on Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions