-
Notifications
You must be signed in to change notification settings - Fork 1
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
OCIS Response is empty when accepting a share #207
Comments
should have been fixed by cs3org/reva#1685 but not all tests got removed from expected to fail, after that fix arrives in ocis we need to double check why the other tests still fail and put them in the correct categories |
Note: this has come to OCIS and the OCIS commit id is being updated in web PR owncloud/web#5179 I will move this issue into the current sprint so that someone looks at the remaining expected-failures to record correctly why they still fail. |
requesting only pending shares does not work for me, I had to request |
At the date of the comment, requesting for pending shares is possible: curl -k -u uu1:uu1 https://localhost:9200/ocs/v2.php/apps/files_sharing//api/v1/shares\?format\=json\&shared_with_me\=true\&state\=1\&include_tags\=false\&format\=json | jq Response: {
"ocs": {
"meta": {
"status": "ok",
"statuscode": 200,
"message": "OK"
},
"data": [
{
"id": "d83ffee2-e418-4530-ab2d-553f9695ab59",
"share_type": 0,
"uid_owner": "admin",
"displayname_owner": "Admin",
"additional_info_owner": "admin@example.org",
"permissions": 1,
"stime": 1622811093,
"parent": "",
"expiration": "",
"token": "",
"uid_file_owner": "admin",
"displayname_file_owner": "Admin",
"additional_info_file_owner": "admin@example.org",
"state": 1,
"path": "/buff_biryani.jpg",
"item_type": "file",
"mimetype": "image/jpeg",
"storage_id": "1284d238-aa92-42ce-bdc4-0b0000009157",
"storage": 0,
"item_source": "MTI4NGQyMzgtYWE5Mi00MmNlLWJkYzQtMGIwMDAwMDA5MTU3OmQ4N2Y1MDA5LTg0OGQtNDJiMC04MTQwLTFhNjlhZTc2YTVkYg==",
"file_source": "MTI4NGQyMzgtYWE5Mi00MmNlLWJkYzQtMGIwMDAwMDA5MTU3OmQ4N2Y1MDA5LTg0OGQtNDJiMC04MTQwLTFhNjlhZTc2YTVkYg==",
"file_parent": "",
"file_target": "/buff_biryani.jpg",
"share_with": "uu1",
"share_with_displayname": "uu1",
"share_with_additional_info": "uu1@oc.cc",
"mail_send": 0,
"name": ""
}
]
}
}
curl -k -u uu1:uu1 -X POST https://localhost:9200/ocs/v2.php/apps/files_sharing/api/v1/shares/pending/d83ffee2-e418-4530-ab2d-553f9695ab59\?format\=json | jq Response: {
"ocs": {
"meta": {
"status": "ok",
"statuscode": 200,
"message": "OK"
},
"data": [
{
"id": "d83ffee2-e418-4530-ab2d-553f9695ab59",
"share_type": 0,
"uid_owner": "admin",
"displayname_owner": "Admin",
"additional_info_owner": "admin@example.org",
"permissions": 1,
"stime": 1622811093,
"parent": "",
"expiration": "",
"token": "",
"uid_file_owner": "admin",
"displayname_file_owner": "Admin",
"additional_info_file_owner": "admin@example.org",
"state": 0,
"path": "/Shares/buff_biryani.jpg",
"item_type": "file",
"mimetype": "image/jpeg",
"storage_id": "1284d238-aa92-42ce-bdc4-0b0000009157",
"storage": 0,
"item_source": "MTI4NGQyMzgtYWE5Mi00MmNlLWJkYzQtMGIwMDAwMDA5MTU3OmQ4N2Y1MDA5LTg0OGQtNDJiMC04MTQwLTFhNjlhZTc2YTVkYg==",
"file_source": "MTI4NGQyMzgtYWE5Mi00MmNlLWJkYzQtMGIwMDAwMDA5MTU3OmQ4N2Y1MDA5LTg0OGQtNDJiMC04MTQwLTFhNjlhZTc2YTVkYg==",
"file_parent": "",
"file_target": "/Shares/buff_biryani.jpg",
"share_with": "uu1",
"share_with_displayname": "uu1",
"share_with_additional_info": "uu1@oc.cc",
"mail_send": 0,
"name": ""
}
]
}
} |
I will check the expected failures (if needs update) on Monday! |
https://github.com/owncloud/core/blob/master/tests/acceptance/features/apiShareManagement/acceptSharesToSharesFolder.feature#L31
Fails with:
Similarly if I do this with
curl
commands:The response to that last command has HTTP status 200, success. But the body is empty. In oC10 there are a whole list of fields with data about the share that was accepted.
This prevents a lot of sharing tests from being able to pass, because shares have to be accepted in OCIS, and the response to accepting a share is missing expected stuff.
The text was updated successfully, but these errors were encountered: