Closed PrajwolAmatya closed 1 year ago
It works when we fisrt set the permission to read
and then update the link to edit
permission, then the enforce-password
config works fine. Is it supposed to have that behavior?
It works when we fisrt set the permission to read and then update the link to edit permission, then the enforce-password config works fine. Is it supposed to have that behavior?
This is the User Flow in the WebUI
The api should also enforce passwords when creating a public share. @kobergj
Describe the bug
While running the API test with config
OCIS_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD
to true, and if we do not set password forupload, edit or contribute
permissions, the returned response is200
.It works fine manually.
Steps to reproduce
Steps to reproduce the behavior:
OCIS_SHARING_PUBLIC_WRITEABLE_SHARE_MUST_HAVE_PASSWORD
to true.testfile.txt
curl -k -X POST https://localhost:9200/ocs/v1.php/apps/files_sharing/api/v1/shares -d'shareType=3&path=/testfile.txt&permissions=3' -uadmin:admin -v
Actual behavior
The response returns status code
200
, and the link is created without password. Actual Response:Now, if we update the public link using command:
curl -k -X PUT https://localhost:9200/ocs/v1.php/apps/files_sharing/api/v1/shares/<share_id> -d'permissions=3' -uadmin:admin -v
Then it returns the response:
Is this the actual behavior?