You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The POST payload should contain a field called sender except in v1.0.0, which is optional.
No sharedBy is in the specification in any version. Please let me know if I'm wrong.
I believe this is a remnant of OCS that has somehow been mixed into the OCM implementation and has remained there until now.
Testing the federated sharing capabilities using OcmStub results in reading the create share POST payload from different EFSS:
I've noticed (testing with OcmStub and Aver) that Nextcloud doesn't receive share data correctly if the share is sent via the fully compliant program, for example, consider this scenario:
Michiel owns the file IETF Draft.md on pondersource.org
Michiel shares it with Mahdi on the same domain.
Mahdi shares the file with Giuseppe on cern.ch
Giuseppe sees Michiel as the sender instead of Mahdi <------ Problem
The root cause of the problem is the way nextcloud parses share requests:
Possible mismatch of the POST request payload to the
/shares
endpoint.Based on OCM API versions:
The POST payload should contain a field called
sender
except inv1.0.0
, which is optional.No
sharedBy
is in the specification in any version. Please let me know if I'm wrong.I believe this is a remnant of OCS that has somehow been mixed into the OCM implementation and has remained there until now.
Testing the federated sharing capabilities using OcmStub results in reading the create share POST payload from different EFSS:
oCIS version 5.0.6: <----- Correct
ownCloud version 10.15.0: <----- Correct
Nextcloud version 30.0.3: <----- Wrong
Nextcloud version 29.0.10: <----- Wrong
NOTICE: The trailing
/
is removed fromowner
andsharedBy
since this versionNextcloud version 28.0.12: <----- Wrong
Nextcloud version 27.1.11: <----- Wrong
I've noticed (testing with OcmStub and Aver) that Nextcloud doesn't receive share data correctly if the share is sent via the fully compliant program, for example, consider this scenario:
IETF Draft.md
onpondersource.org
cern.ch
The root cause of the problem is the way nextcloud parses share requests:
This is from Nextcloud version 27.1.11 Share payload object
So, if a fully compliant program sends a POST request with
sender
andsenderDisplayName
, Nextcloud would simply fall back to using the owner as the senderThere is a PR for fixing this:
nextcloud/server#47199
Anyway, it wasn't complying with v1.0.0 either, so it's not about the new changes in v1.1.0 of the API.
The text was updated successfully, but these errors were encountered: