RequestShare: Introduce the notion of a share request#194
RequestShare: Introduce the notion of a share request#194mickenordin wants to merge 4 commits intodevelopfrom
Conversation
Signed-off-by: Micke Nordin <kano@sunet.se>
| Consumer specific identifier of the user, group or federation that | ||
| wants to recive a share of the resource. | ||
| example: 51dc30ddc473d43a6011e9ebba6ca770@geant.org | ||
| shareId: |
There was a problem hiding this comment.
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) |
There was a problem hiding this comment.
I guess that should be httpsig [RFC9421]
glpatcern
left a comment
glpatcern
left a comment
There was a problem hiding this comment.
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: "51dc30ddc473d43a6011e9ebba6ca770@geant.org" | ||
| * REQUIRED shareId (string) |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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 <giuseppe.lopresti@cern.ch>
Co-authored-by: Giuseppe Lo Presti <giuseppe.lopresti@cern.ch>
Co-authored-by: Giuseppe Lo Presti <giuseppe.lopresti@cern.ch>
3 participants
No description provided.