-
Notifications
You must be signed in to change notification settings - Fork 16
RequestShare: Introduce the notion of a share request #194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
Signed-off-by: Micke Nordin <[email protected]>
| Consumer specific identifier of the user, group or federation that | ||
| wants to recive a share of the resource. | ||
| example: [email protected] | ||
| shareId: |
There was a problem hiding this comment.
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) |
There was a problem hiding this comment.
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]
There was a problem hiding this 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) |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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]>
Co-authored-by: Giuseppe Lo Presti <[email protected]>
Co-authored-by: Giuseppe Lo Presti <[email protected]>
No description provided.