Skip to content

Conversation

@mickenordin
Copy link
Collaborator

No description provided.

@mickenordin mickenordin marked this pull request as ready for review June 13, 2025 07:25
Consumer specific identifier of the user, group or federation that
wants to recive a share of the resource.
example: [email protected]
shareId:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the same as providerId in NewShare ?

* using `application/json` as the `Content-Type` HTTP request header
* its request body containing a JSON document representing an object with the fields as described below
* using TLS
* using [httpsig](https://datatracker.ietf.org/doc/html/draft-cavage-http-signatures-12)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess that should be httpsig [RFC9421]

Copy link
Member

@glpatcern glpatcern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I went for a review of this new flow, hope I have understood the rationale, and of course all open for further comments.

Consumer specific identifier of the user, group or federation that
wants to recive a share of the resource.
Example: "[email protected]"
* REQUIRED shareId (string)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here we have a problem: a receiver won't know the (opaque) ID of a remote resource, but only a path (or something "human readable"?). Shall we name this simply share, or sharePath?

A unique identifier for the resource.
Example: 1234567890abcdef

After receiving a request for a Share, the Sending Party MAY send a Share Creation Notification to the Sending Party using the OCM address in the shareWith field.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here I'd imagine the flow to be async: the server would respond HTTP 202 Accepted, signifying that the sender user was notified about the request to share. Once they accept, the normal Share Notification will take place.

Co-authored-by: Giuseppe Lo Presti <[email protected]>
mickenordin and others added 2 commits September 9, 2025 11:13
Co-authored-by: Giuseppe Lo Presti <[email protected]>
Co-authored-by: Giuseppe Lo Presti <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants