when:
matrix:
TESTS: integration-sharing-v1
+ integration-sharing-v1-part2:
+ image: nextcloudci/integration-php7.0:integration-php7.0-3
+ commands:
+ - ./occ maintenance:install --admin-pass=admin
+ - cd build/integration
+ - ./run.sh features/sharing-v1-part2.feature
+ when:
+ matrix:
+ TESTS: integration-sharing-v1-part2
integration-checksums-v1:
image: nextcloudci/integration-php7.0:integration-php7.0-3
commands:
- TESTS: integration-dav-v2
- TESTS: integration-ocs-v1
- TESTS: integration-sharing-v1
+ - TESTS: integration-sharing-v1-part2
- TESTS: integration-checksums
- TESTS: integration-external-storage
- TESTS: integration-provisioning-v1
--- /dev/null
+Feature: sharing
+ Background:
+ Given using api version "1"
+ Given using old dav path
+
+# See sharing-v1.feature
+
+ Scenario: getting all shares of a file with reshares
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user2" exists
+ And user "user3" exists
+ And file "textfile0.txt" of user "user0" is shared with user "user1"
+ And file "textfile0 (2).txt" of user "user1" is shared with user "user2"
+ And As an "user0"
+ When sending "GET" to "/apps/files_sharing/api/v1/shares?reshares=true&path=textfile0.txt"
+ Then the OCS status code should be "100"
+ And the HTTP status code should be "200"
+ And User "user1" should be included in the response
+ And User "user2" should be included in the response
+ And User "user3" should not be included in the response
+
+ Scenario: Reshared files can be still accessed if a user in the middle removes it.
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user2" exists
+ And user "user3" exists
+ And file "textfile0.txt" of user "user0" is shared with user "user1"
+ And file "textfile0 (2).txt" of user "user1" is shared with user "user2"
+ And file "textfile0 (2).txt" of user "user2" is shared with user "user3"
+ And As an "user1"
+ When User "user1" deletes file "/textfile0 (2).txt"
+ And As an "user3"
+ And Downloading file "/textfile0 (2).txt" with range "bytes=1-8"
+ Then Downloaded content should be "extcloud"
+
+ Scenario: getting share info of a share
+ Given user "user0" exists
+ And user "user1" exists
+ And file "textfile0.txt" of user "user0" is shared with user "user1"
+ And As an "user0"
+ When Getting info of last share
+ Then the OCS status code should be "100"
+ And the HTTP status code should be "200"
+ And Share fields of last share match with
+ | id | A_NUMBER |
+ | item_type | file |
+ | item_source | A_NUMBER |
+ | share_type | 0 |
+ | share_with | user1 |
+ | file_source | A_NUMBER |
+ | file_target | /textfile0.txt |
+ | path | /textfile0.txt |
+ | permissions | 19 |
+ | stime | A_NUMBER |
+ | storage | A_NUMBER |
+ | mail_send | 0 |
+ | uid_owner | user0 |
+ | storage_id | home::user0 |
+ | file_parent | A_NUMBER |
+ | share_with_displayname | user1 |
+ | displayname_owner | user0 |
+ | mimetype | text/plain |
+
+ Scenario: keep group permissions in sync
+ Given As an "admin"
+ Given user "user0" exists
+ And user "user1" exists
+ And group "group1" exists
+ And user "user1" belongs to group "group1"
+ And file "textfile0.txt" of user "user0" is shared with group "group1"
+ And User "user1" moved file "/textfile0.txt" to "/FOLDER/textfile0.txt"
+ And As an "user0"
+ When Updating last share with
+ | permissions | 1 |
+ And Getting info of last share
+ Then the OCS status code should be "100"
+ And the HTTP status code should be "200"
+ And Share fields of last share match with
+ | id | A_NUMBER |
+ | item_type | file |
+ | item_source | A_NUMBER |
+ | share_type | 1 |
+ | file_source | A_NUMBER |
+ | file_target | /textfile0.txt |
+ | permissions | 1 |
+ | stime | A_NUMBER |
+ | storage | A_NUMBER |
+ | mail_send | 0 |
+ | uid_owner | user0 |
+ | storage_id | home::user0 |
+ | file_parent | A_NUMBER |
+ | displayname_owner | user0 |
+ | mimetype | text/plain |
+
+ Scenario: Sharee can see the share
+ Given user "user0" exists
+ And user "user1" exists
+ And file "textfile0.txt" of user "user0" is shared with user "user1"
+ And As an "user1"
+ When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
+ Then the OCS status code should be "100"
+ And the HTTP status code should be "200"
+ And last share_id is included in the answer
+
+ Scenario: Sharee can see the filtered share
+ Given user "user0" exists
+ And user "user1" exists
+ And file "textfile0.txt" of user "user0" is shared with user "user1"
+ And file "textfile1.txt" of user "user0" is shared with user "user1"
+ And As an "user1"
+ When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true&path=textfile1 (2).txt"
+ Then the OCS status code should be "100"
+ And the HTTP status code should be "200"
+ And last share_id is included in the answer
+
+ Scenario: Sharee can't see the share that is filtered out
+ Given user "user0" exists
+ And user "user1" exists
+ And file "textfile0.txt" of user "user0" is shared with user "user1"
+ And file "textfile1.txt" of user "user0" is shared with user "user1"
+ And As an "user1"
+ When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true&path=textfile0 (2).txt"
+ Then the OCS status code should be "100"
+ And the HTTP status code should be "200"
+ And last share_id is not included in the answer
+
+ Scenario: Sharee can see the group share
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "group0" exists
+ And user "user1" belongs to group "group0"
+ And file "textfile0.txt" of user "user0" is shared with group "group0"
+ And As an "user1"
+ When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
+ Then the OCS status code should be "100"
+ And the HTTP status code should be "200"
+ And last share_id is included in the answer
+
+ Scenario: User is not allowed to reshare file
+ As an "admin"
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user2" exists
+ And As an "user0"
+ And creating a share with
+ | path | /textfile0.txt |
+ | shareType | 0 |
+ | shareWith | user1 |
+ | permissions | 8 |
+ And As an "user1"
+ When creating a share with
+ | path | /textfile0 (2).txt |
+ | shareType | 0 |
+ | shareWith | user2 |
+ | permissions | 31 |
+ Then the OCS status code should be "404"
+ And the HTTP status code should be "200"
+
+ Scenario: User is not allowed to reshare file with more permissions
+ As an "admin"
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user2" exists
+ And As an "user0"
+ And creating a share with
+ | path | /textfile0.txt |
+ | shareType | 0 |
+ | shareWith | user1 |
+ | permissions | 16 |
+ And As an "user1"
+ When creating a share with
+ | path | /textfile0 (2).txt |
+ | shareType | 0 |
+ | shareWith | user2 |
+ | permissions | 31 |
+ Then the OCS status code should be "404"
+ And the HTTP status code should be "200"
+
+ Scenario: Get a share with a user which didn't received the share
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user2" exists
+ And file "textfile0.txt" of user "user0" is shared with user "user1"
+ And As an "user2"
+ When Getting info of last share
+ Then the OCS status code should be "404"
+ And the HTTP status code should be "200"
+
+ Scenario: Share of folder and sub-folder to same user - core#20645
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "group0" exists
+ And user "user1" belongs to group "group0"
+ And file "/PARENT" of user "user0" is shared with user "user1"
+ When file "/PARENT/CHILD" of user "user0" is shared with group "group0"
+ Then user "user1" should see following elements
+ | /FOLDER/ |
+ | /PARENT/ |
+ | /CHILD/ |
+ | /PARENT/parent.txt |
+ | /CHILD/child.txt |
+ And the HTTP status code should be "200"
+
+ Scenario: Share a file by multiple channels
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And user "user2" exists
+ And group "group0" exists
+ And user "user1" belongs to group "group0"
+ And user "user2" belongs to group "group0"
+ And user "user0" created a folder "/common"
+ And user "user0" created a folder "/common/sub"
+ And file "common" of user "user0" is shared with group "group0"
+ And file "textfile0.txt" of user "user1" is shared with user "user2"
+ And User "user1" moved file "/textfile0.txt" to "/common/textfile0.txt"
+ And User "user1" moved file "/common/textfile0.txt" to "/common/sub/textfile0.txt"
+ And As an "user2"
+ When Downloading file "/common/sub/textfile0.txt" with range "bytes=10-18"
+ Then Downloaded content should be "test text"
+ And Downloaded content when downloading file "/textfile0.txt" with range "bytes=10-18" should be "test text"
+ And user "user2" should see following elements
+ | /common/sub/textfile0.txt |
+
+ Scenario: Share a file by multiple channels
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And user "user2" exists
+ And group "group0" exists
+ And user "user1" belongs to group "group0"
+ And user "user2" belongs to group "group0"
+ And user "user0" created a folder "/common"
+ And user "user0" created a folder "/common/sub"
+ And file "common" of user "user0" is shared with group "group0"
+ And file "textfile0.txt" of user "user1" is shared with user "user2"
+ And User "user1" moved file "/textfile0.txt" to "/common/textfile0.txt"
+ And User "user1" moved file "/common/textfile0.txt" to "/common/sub/textfile0.txt"
+ And As an "user2"
+ When Downloading file "/textfile0.txt" with range "bytes=10-18"
+ Then Downloaded content should be "test text"
+ And user "user2" should see following elements
+ | /common/sub/textfile0.txt |
+
+ Scenario: Delete all group shares
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "group1" exists
+ And user "user1" belongs to group "group1"
+ And file "textfile0.txt" of user "user0" is shared with group "group1"
+ And User "user1" moved file "/textfile0.txt" to "/FOLDER/textfile0.txt"
+ And As an "user0"
+ And Deleting last share
+ And As an "user1"
+ When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
+ Then the OCS status code should be "100"
+ And the HTTP status code should be "200"
+ And last share_id is not included in the answer
+
+ Scenario: delete a share
+ Given user "user0" exists
+ And user "user1" exists
+ And file "textfile0.txt" of user "user0" is shared with user "user1"
+ And As an "user0"
+ When Deleting last share
+ Then the OCS status code should be "100"
+ And the HTTP status code should be "200"
+
+ Scenario: Keep usergroup shares (#22143)
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And user "user2" exists
+ And group "group" exists
+ And user "user1" belongs to group "group"
+ And user "user2" belongs to group "group"
+ And user "user0" created a folder "/TMP"
+ And file "TMP" of user "user0" is shared with group "group"
+ And user "user1" created a folder "/myFOLDER"
+ And User "user1" moves file "/TMP" to "/myFOLDER/myTMP"
+ And user "user2" does not exist
+ And user "user1" should see following elements
+ | /myFOLDER/myTMP/ |
+
+ Scenario: Check quota of owners parent directory of a shared file
+ Given using old dav path
+ And As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And user "user1" has a quota of "0"
+ And User "user0" moved file "/welcome.txt" to "/myfile.txt"
+ And file "myfile.txt" of user "user0" is shared with user "user1"
+ When User "user1" uploads file "data/textfile.txt" to "/myfile.txt"
+ Then the HTTP status code should be "204"
+
+ Scenario: Don't allow sharing of the root
+ Given user "user0" exists
+ And As an "user0"
+ When creating a share with
+ | path | / |
+ | shareType | 3 |
+ Then the OCS status code should be "403"
+
+ Scenario: Allow modification of reshare
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user2" exists
+ And user "user0" created a folder "/TMP"
+ And file "TMP" of user "user0" is shared with user "user1"
+ And file "TMP" of user "user1" is shared with user "user2"
+ And As an "user1"
+ When Updating last share with
+ | permissions | 1 |
+ Then the OCS status code should be "100"
+
+ Scenario: Do not allow reshare to exceed permissions
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user2" exists
+ And user "user0" created a folder "/TMP"
+ And As an "user0"
+ And creating a share with
+ | path | /TMP |
+ | shareType | 0 |
+ | shareWith | user1 |
+ | permissions | 21 |
+ And As an "user1"
+ And creating a share with
+ | path | /TMP |
+ | shareType | 0 |
+ | shareWith | user2 |
+ | permissions | 21 |
+ When Updating last share with
+ | permissions | 31 |
+ Then the OCS status code should be "404"
+
+ Scenario: Only allow 1 link share per file/folder
+ Given user "user0" exists
+ And As an "user0"
+ And creating a share with
+ | path | welcome.txt |
+ | shareType | 3 |
+ When save last share id
+ And creating a share with
+ | path | welcome.txt |
+ | shareType | 3 |
+ Then share ids should match
+
+ Scenario: Correct webdav share-permissions for owned file
+ Given user "user0" exists
+ And User "user0" uploads file with content "foo" to "/tmp.txt"
+ When as "user0" gets properties of folder "/tmp.txt" with
+ |{http://open-collaboration-services.org/ns}share-permissions |
+ Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "19"
+
+ Scenario: Correct webdav share-permissions for received file with edit and reshare permissions
+ Given user "user0" exists
+ And user "user1" exists
+ And User "user0" uploads file with content "foo" to "/tmp.txt"
+ And file "/tmp.txt" of user "user0" is shared with user "user1"
+ When as "user1" gets properties of folder "/tmp.txt" with
+ |{http://open-collaboration-services.org/ns}share-permissions |
+ Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "19"
+
+ Scenario: Correct webdav share-permissions for received file with edit permissions but no reshare permissions
+ Given user "user0" exists
+ And user "user1" exists
+ And User "user0" uploads file with content "foo" to "/tmp.txt"
+ And file "tmp.txt" of user "user0" is shared with user "user1"
+ And As an "user0"
+ And Updating last share with
+ | permissions | 3 |
+ When as "user1" gets properties of folder "/tmp.txt" with
+ |{http://open-collaboration-services.org/ns}share-permissions |
+ Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "3"
+
+ Scenario: Correct webdav share-permissions for received file with reshare permissions but no edit permissions
+ Given user "user0" exists
+ And user "user1" exists
+ And User "user0" uploads file with content "foo" to "/tmp.txt"
+ And file "tmp.txt" of user "user0" is shared with user "user1"
+ And As an "user0"
+ And Updating last share with
+ | permissions | 17 |
+ When as "user1" gets properties of folder "/tmp.txt" with
+ |{http://open-collaboration-services.org/ns}share-permissions |
+ Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "17"
+
+ Scenario: Correct webdav share-permissions for owned folder
+ Given user "user0" exists
+ And user "user0" created a folder "/tmp"
+ When as "user0" gets properties of folder "/" with
+ |{http://open-collaboration-services.org/ns}share-permissions |
+ Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "31"
+
+ Scenario: Correct webdav share-permissions for received folder with all permissions
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user0" created a folder "/tmp"
+ And file "/tmp" of user "user0" is shared with user "user1"
+ When as "user1" gets properties of folder "/tmp" with
+ |{http://open-collaboration-services.org/ns}share-permissions |
+ Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "31"
+
+ Scenario: Correct webdav share-permissions for received folder with all permissions but edit
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user0" created a folder "/tmp"
+ And file "/tmp" of user "user0" is shared with user "user1"
+ And As an "user0"
+ And Updating last share with
+ | permissions | 29 |
+ When as "user1" gets properties of folder "/tmp" with
+ |{http://open-collaboration-services.org/ns}share-permissions |
+ Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "29"
+
+ Scenario: Correct webdav share-permissions for received folder with all permissions but create
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user0" created a folder "/tmp"
+ And file "/tmp" of user "user0" is shared with user "user1"
+ And As an "user0"
+ And Updating last share with
+ | permissions | 27 |
+ When as "user1" gets properties of folder "/tmp" with
+ |{http://open-collaboration-services.org/ns}share-permissions |
+ Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "27"
+
+ Scenario: Correct webdav share-permissions for received folder with all permissions but delete
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user0" created a folder "/tmp"
+ And file "/tmp" of user "user0" is shared with user "user1"
+ And As an "user0"
+ And Updating last share with
+ | permissions | 23 |
+ When as "user1" gets properties of folder "/tmp" with
+ |{http://open-collaboration-services.org/ns}share-permissions |
+ Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "23"
+
+ Scenario: Correct webdav share-permissions for received folder with all permissions but share
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user0" created a folder "/tmp"
+ And file "/tmp" of user "user0" is shared with user "user1"
+ And As an "user0"
+ And Updating last share with
+ | permissions | 15 |
+ When as "user1" gets properties of folder "/tmp" with
+ |{http://open-collaboration-services.org/ns}share-permissions |
+ Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "15"
+
+ Scenario: unique target names for incoming shares
+ Given user "user0" exists
+ And user "user1" exists
+ And user "user2" exists
+ And user "user0" created a folder "/foo"
+ And user "user1" created a folder "/foo"
+ When file "/foo" of user "user0" is shared with user "user2"
+ And file "/foo" of user "user1" is shared with user "user2"
+ Then user "user2" should see following elements
+ | /foo/ |
+ | /foo%20(2)/ |
+
+ Scenario: Creating a new share with a disabled user
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And assure user "user0" is disabled
+ And As an "user0"
+ When sending "POST" to "/apps/files_sharing/api/v1/shares" with
+ | path | welcome.txt |
+ | shareWith | user1 |
+ | shareType | 0 |
+ Then the OCS status code should be "997"
+ And the HTTP status code should be "401"
+
+ Scenario: Deleting a group share as user
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "group1" exists
+ And user "user1" belongs to group "group1"
+ And As an "user0"
+ And creating a share with
+ | path | welcome.txt |
+ | shareType | 1 |
+ | shareWith | group1 |
+ When As an "user1"
+ And Deleting last share
+ Then the OCS status code should be "100"
+ And the HTTP status code should be "200"
+
+ Scenario: Merging shares for recipient when shared from outside with group and member
+ Given using old dav path
+ And As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "group1" exists
+ And user "user1" belongs to group "group1"
+ And user "user0" created a folder "/merge-test-outside"
+ When folder "/merge-test-outside" of user "user0" is shared with group "group1"
+ And folder "/merge-test-outside" of user "user0" is shared with user "user1"
+ Then as "user1" the folder "/merge-test-outside" exists
+ And as "user1" the folder "/merge-test-outside (2)" does not exist
+
+ Scenario: Merging shares for recipient when shared from outside with group and member with different permissions
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "group1" exists
+ And user "user1" belongs to group "group1"
+ And user "user0" created a folder "/merge-test-outside-perms"
+ When folder "/merge-test-outside-perms" of user "user0" is shared with group "group1" with permissions 1
+ And folder "/merge-test-outside-perms" of user "user0" is shared with user "user1" with permissions 31
+ Then as "user1" gets properties of folder "/merge-test-outside-perms" with
+ |{http://owncloud.org/ns}permissions|
+ And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
+ And as "user1" the folder "/merge-test-outside-perms (2)" does not exist
+
+ Scenario: Merging shares for recipient when shared from outside with two groups
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "group1" exists
+ And group "group2" exists
+ And user "user1" belongs to group "group1"
+ And user "user1" belongs to group "group2"
+ And user "user0" created a folder "/merge-test-outside-twogroups"
+ When folder "/merge-test-outside-twogroups" of user "user0" is shared with group "group1"
+ And folder "/merge-test-outside-twogroups" of user "user0" is shared with group "group2"
+ Then as "user1" the folder "/merge-test-outside-twogroups" exists
+ And as "user1" the folder "/merge-test-outside-twogroups (2)" does not exist
+
+ Scenario: Merging shares for recipient when shared from outside with two groups with different permissions
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "group1" exists
+ And group "group2" exists
+ And user "user1" belongs to group "group1"
+ And user "user1" belongs to group "group2"
+ And user "user0" created a folder "/merge-test-outside-twogroups-perms"
+ When folder "/merge-test-outside-twogroups-perms" of user "user0" is shared with group "group1" with permissions 1
+ And folder "/merge-test-outside-twogroups-perms" of user "user0" is shared with group "group2" with permissions 31
+ Then as "user1" gets properties of folder "/merge-test-outside-twogroups-perms" with
+ |{http://owncloud.org/ns}permissions|
+ And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
+ And as "user1" the folder "/merge-test-outside-twogroups-perms (2)" does not exist
+
+ Scenario: Merging shares for recipient when shared from outside with two groups and member
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "group1" exists
+ And group "group2" exists
+ And user "user1" belongs to group "group1"
+ And user "user1" belongs to group "group2"
+ And user "user0" created a folder "/merge-test-outside-twogroups-member-perms"
+ When folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with group "group1" with permissions 1
+ And folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with group "group2" with permissions 31
+ And folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with user "user1" with permissions 1
+ Then as "user1" gets properties of folder "/merge-test-outside-twogroups-member-perms" with
+ |{http://owncloud.org/ns}permissions|
+ And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
+ And as "user1" the folder "/merge-test-outside-twogroups-member-perms (2)" does not exist
+
+ Scenario: Merging shares for recipient when shared from inside with group
+ Given As an "admin"
+ And user "user0" exists
+ And group "group1" exists
+ And user "user0" belongs to group "group1"
+ And user "user0" created a folder "/merge-test-inside-group"
+ When folder "/merge-test-inside-group" of user "user0" is shared with group "group1"
+ Then as "user0" the folder "/merge-test-inside-group" exists
+ And as "user0" the folder "/merge-test-inside-group (2)" does not exist
+
+ Scenario: Merging shares for recipient when shared from inside with two groups
+ Given As an "admin"
+ And user "user0" exists
+ And group "group1" exists
+ And group "group2" exists
+ And user "user0" belongs to group "group1"
+ And user "user0" belongs to group "group2"
+ And user "user0" created a folder "/merge-test-inside-twogroups"
+ When folder "/merge-test-inside-twogroups" of user "user0" is shared with group "group1"
+ And folder "/merge-test-inside-twogroups" of user "user0" is shared with group "group2"
+ Then as "user0" the folder "/merge-test-inside-twogroups" exists
+ And as "user0" the folder "/merge-test-inside-twogroups (2)" does not exist
+ And as "user0" the folder "/merge-test-inside-twogroups (3)" does not exist
+
+ Scenario: Merging shares for recipient when shared from inside with group with less permissions
+ Given As an "admin"
+ And user "user0" exists
+ And group "group1" exists
+ And group "group2" exists
+ And user "user0" belongs to group "group1"
+ And user "user0" belongs to group "group2"
+ And user "user0" created a folder "/merge-test-inside-twogroups-perms"
+ When folder "/merge-test-inside-twogroups-perms" of user "user0" is shared with group "group1"
+ And folder "/merge-test-inside-twogroups-perms" of user "user0" is shared with group "group2"
+ Then as "user0" gets properties of folder "/merge-test-inside-twogroups-perms" with
+ |{http://owncloud.org/ns}permissions|
+ And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "RDNVCK"
+ And as "user0" the folder "/merge-test-inside-twogroups-perms (2)" does not exist
+ And as "user0" the folder "/merge-test-inside-twogroups-perms (3)" does not exist
+
+ Scenario: Merging shares for recipient when shared from outside with group then user and recipient renames in between
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "group1" exists
+ And user "user1" belongs to group "group1"
+ And user "user0" created a folder "/merge-test-outside-groups-renamebeforesecondshare"
+ When folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with group "group1"
+ And User "user1" moved folder "/merge-test-outside-groups-renamebeforesecondshare" to "/merge-test-outside-groups-renamebeforesecondshare-renamed"
+ And Sleep for "1" seconds
+ And folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with user "user1"
+ Then as "user1" gets properties of folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" with
+ |{http://owncloud.org/ns}permissions|
+ And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
+ And as "user1" the folder "/merge-test-outside-groups-renamebeforesecondshare" does not exist
+
+ Scenario: Merging shares for recipient when shared from outside with user then group and recipient renames in between
+ Given using old dav path
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "group1" exists
+ And user "user1" belongs to group "group1"
+ And user "user0" created a folder "/merge-test-outside-groups-renamebeforesecondshare"
+ When folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with user "user1"
+ And User "user1" moved folder "/merge-test-outside-groups-renamebeforesecondshare" to "/merge-test-outside-groups-renamebeforesecondshare-renamed"
+ And Sleep for "1" seconds
+ And folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with group "group1"
+ Then as "user1" gets properties of folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" with
+ |{http://owncloud.org/ns}permissions|
+ And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
+ And as "user1" the folder "/merge-test-outside-groups-renamebeforesecondshare" does not exist
+
+ Scenario: Empting trashbin
+ Given As an "admin"
+ And user "user0" exists
+ And User "user0" deletes file "/textfile0.txt"
+ When User "user0" empties trashbin
+ Then the HTTP status code should be "200"
+
+ Scenario: orphaned shares
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And user "user0" created a folder "/common"
+ And user "user0" created a folder "/common/sub"
+ And file "/common/sub" of user "user0" is shared with user "user1"
+ And User "user0" deletes folder "/common"
+ When User "user0" empties trashbin
+ Then as "user1" the folder "/sub" does not exist
+
+ Scenario: sharing again an own file while belonging to a group
+ Given As an "admin"
+ Given user "user0" exists
+ And group "sharing-group" exists
+ And user "user0" belongs to group "sharing-group"
+ And file "welcome.txt" of user "user0" is shared with group "sharing-group"
+ And Deleting last share
+ When sending "POST" to "/apps/files_sharing/api/v1/shares" with
+ | path | welcome.txt |
+ | shareWith | sharing-group |
+ | shareType | 1 |
+ Then the OCS status code should be "100"
+ And the HTTP status code should be "200"
+
+ Scenario: unshare from self
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And group "sharing-group" exists
+ And user "user0" belongs to group "sharing-group"
+ And user "user1" belongs to group "sharing-group"
+ And file "/PARENT/parent.txt" of user "user0" is shared with group "sharing-group"
+ And user "user0" stores etag of element "/PARENT"
+ And user "user1" stores etag of element "/"
+ And As an "user1"
+ When Deleting last share
+ Then etag of element "/" of user "user1" has changed
+ And etag of element "/PARENT" of user "user0" has not changed
+
+ Scenario: do not allow to increase link share permissions on reshare
+ Given As an "admin"
+ And user "admin" created a folder "/TMP"
+ And user "user0" exists
+ And creating a share with
+ | path | TMP |
+ | shareType | 0 |
+ | shareWith | user0 |
+ | permissions | 17 |
+ When As an "user0"
+ And creating a share with
+ | path | TMP |
+ | shareType | 3 |
+ And Updating last share with
+ | publicUpload | true |
+ Then the OCS status code should be "404"
+
+ Scenario: moving a file into a share as recipient
+ Given As an "admin"
+ And user "user0" exists
+ And user "user1" exists
+ And user "user0" created a folder "/shared"
+ And folder "/shared" of user "user0" is shared with user "user1"
+ When User "user1" moved file "/textfile0.txt" to "/shared/shared_file.txt"
+ Then as "user1" the file "/shared/shared_file.txt" exists
+ And as "user0" the file "/shared/shared_file.txt" exists
\ No newline at end of file
And User "user2" should be included in the response
And User "user3" should not be included in the response
- Scenario: getting all shares of a file with reshares
- Given user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And user "user3" exists
- And file "textfile0.txt" of user "user0" is shared with user "user1"
- And file "textfile0 (2).txt" of user "user1" is shared with user "user2"
- And As an "user0"
- When sending "GET" to "/apps/files_sharing/api/v1/shares?reshares=true&path=textfile0.txt"
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
- And User "user1" should be included in the response
- And User "user2" should be included in the response
- And User "user3" should not be included in the response
-
- Scenario: Reshared files can be still accessed if a user in the middle removes it.
- Given user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And user "user3" exists
- And file "textfile0.txt" of user "user0" is shared with user "user1"
- And file "textfile0 (2).txt" of user "user1" is shared with user "user2"
- And file "textfile0 (2).txt" of user "user2" is shared with user "user3"
- And As an "user1"
- When User "user1" deletes file "/textfile0 (2).txt"
- And As an "user3"
- And Downloading file "/textfile0 (2).txt" with range "bytes=1-8"
- Then Downloaded content should be "extcloud"
-
- Scenario: getting share info of a share
- Given user "user0" exists
- And user "user1" exists
- And file "textfile0.txt" of user "user0" is shared with user "user1"
- And As an "user0"
- When Getting info of last share
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
- And Share fields of last share match with
- | id | A_NUMBER |
- | item_type | file |
- | item_source | A_NUMBER |
- | share_type | 0 |
- | share_with | user1 |
- | file_source | A_NUMBER |
- | file_target | /textfile0.txt |
- | path | /textfile0.txt |
- | permissions | 19 |
- | stime | A_NUMBER |
- | storage | A_NUMBER |
- | mail_send | 0 |
- | uid_owner | user0 |
- | storage_id | home::user0 |
- | file_parent | A_NUMBER |
- | share_with_displayname | user1 |
- | displayname_owner | user0 |
- | mimetype | text/plain |
-
- Scenario: keep group permissions in sync
- Given As an "admin"
- Given user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And file "textfile0.txt" of user "user0" is shared with group "group1"
- And User "user1" moved file "/textfile0.txt" to "/FOLDER/textfile0.txt"
- And As an "user0"
- When Updating last share with
- | permissions | 1 |
- And Getting info of last share
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
- And Share fields of last share match with
- | id | A_NUMBER |
- | item_type | file |
- | item_source | A_NUMBER |
- | share_type | 1 |
- | file_source | A_NUMBER |
- | file_target | /textfile0.txt |
- | permissions | 1 |
- | stime | A_NUMBER |
- | storage | A_NUMBER |
- | mail_send | 0 |
- | uid_owner | user0 |
- | storage_id | home::user0 |
- | file_parent | A_NUMBER |
- | displayname_owner | user0 |
- | mimetype | text/plain |
-
- Scenario: Sharee can see the share
- Given user "user0" exists
- And user "user1" exists
- And file "textfile0.txt" of user "user0" is shared with user "user1"
- And As an "user1"
- When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
- And last share_id is included in the answer
-
- Scenario: Sharee can see the filtered share
- Given user "user0" exists
- And user "user1" exists
- And file "textfile0.txt" of user "user0" is shared with user "user1"
- And file "textfile1.txt" of user "user0" is shared with user "user1"
- And As an "user1"
- When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true&path=textfile1 (2).txt"
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
- And last share_id is included in the answer
-
- Scenario: Sharee can't see the share that is filtered out
- Given user "user0" exists
- And user "user1" exists
- And file "textfile0.txt" of user "user0" is shared with user "user1"
- And file "textfile1.txt" of user "user0" is shared with user "user1"
- And As an "user1"
- When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true&path=textfile0 (2).txt"
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
- And last share_id is not included in the answer
-
- Scenario: Sharee can see the group share
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group0" exists
- And user "user1" belongs to group "group0"
- And file "textfile0.txt" of user "user0" is shared with group "group0"
- And As an "user1"
- When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
- And last share_id is included in the answer
-
- Scenario: User is not allowed to reshare file
- As an "admin"
- Given user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And As an "user0"
- And creating a share with
- | path | /textfile0.txt |
- | shareType | 0 |
- | shareWith | user1 |
- | permissions | 8 |
- And As an "user1"
- When creating a share with
- | path | /textfile0 (2).txt |
- | shareType | 0 |
- | shareWith | user2 |
- | permissions | 31 |
- Then the OCS status code should be "404"
- And the HTTP status code should be "200"
-
- Scenario: User is not allowed to reshare file with more permissions
- As an "admin"
- Given user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And As an "user0"
- And creating a share with
- | path | /textfile0.txt |
- | shareType | 0 |
- | shareWith | user1 |
- | permissions | 16 |
- And As an "user1"
- When creating a share with
- | path | /textfile0 (2).txt |
- | shareType | 0 |
- | shareWith | user2 |
- | permissions | 31 |
- Then the OCS status code should be "404"
- And the HTTP status code should be "200"
-
- Scenario: Get a share with a user which didn't received the share
- Given user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And file "textfile0.txt" of user "user0" is shared with user "user1"
- And As an "user2"
- When Getting info of last share
- Then the OCS status code should be "404"
- And the HTTP status code should be "200"
-
- Scenario: Share of folder and sub-folder to same user - core#20645
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group0" exists
- And user "user1" belongs to group "group0"
- And file "/PARENT" of user "user0" is shared with user "user1"
- When file "/PARENT/CHILD" of user "user0" is shared with group "group0"
- Then user "user1" should see following elements
- | /FOLDER/ |
- | /PARENT/ |
- | /CHILD/ |
- | /PARENT/parent.txt |
- | /CHILD/child.txt |
- And the HTTP status code should be "200"
-
- Scenario: Share a file by multiple channels
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And group "group0" exists
- And user "user1" belongs to group "group0"
- And user "user2" belongs to group "group0"
- And user "user0" created a folder "/common"
- And user "user0" created a folder "/common/sub"
- And file "common" of user "user0" is shared with group "group0"
- And file "textfile0.txt" of user "user1" is shared with user "user2"
- And User "user1" moved file "/textfile0.txt" to "/common/textfile0.txt"
- And User "user1" moved file "/common/textfile0.txt" to "/common/sub/textfile0.txt"
- And As an "user2"
- When Downloading file "/common/sub/textfile0.txt" with range "bytes=10-18"
- Then Downloaded content should be "test text"
- And Downloaded content when downloading file "/textfile0.txt" with range "bytes=10-18" should be "test text"
- And user "user2" should see following elements
- | /common/sub/textfile0.txt |
-
- Scenario: Share a file by multiple channels
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And group "group0" exists
- And user "user1" belongs to group "group0"
- And user "user2" belongs to group "group0"
- And user "user0" created a folder "/common"
- And user "user0" created a folder "/common/sub"
- And file "common" of user "user0" is shared with group "group0"
- And file "textfile0.txt" of user "user1" is shared with user "user2"
- And User "user1" moved file "/textfile0.txt" to "/common/textfile0.txt"
- And User "user1" moved file "/common/textfile0.txt" to "/common/sub/textfile0.txt"
- And As an "user2"
- When Downloading file "/textfile0.txt" with range "bytes=10-18"
- Then Downloaded content should be "test text"
- And user "user2" should see following elements
- | /common/sub/textfile0.txt |
-
- Scenario: Delete all group shares
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And file "textfile0.txt" of user "user0" is shared with group "group1"
- And User "user1" moved file "/textfile0.txt" to "/FOLDER/textfile0.txt"
- And As an "user0"
- And Deleting last share
- And As an "user1"
- When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
- And last share_id is not included in the answer
-
- Scenario: delete a share
- Given user "user0" exists
- And user "user1" exists
- And file "textfile0.txt" of user "user0" is shared with user "user1"
- And As an "user0"
- When Deleting last share
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
-
- Scenario: Keep usergroup shares (#22143)
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And group "group" exists
- And user "user1" belongs to group "group"
- And user "user2" belongs to group "group"
- And user "user0" created a folder "/TMP"
- And file "TMP" of user "user0" is shared with group "group"
- And user "user1" created a folder "/myFOLDER"
- And User "user1" moves file "/TMP" to "/myFOLDER/myTMP"
- And user "user2" does not exist
- And user "user1" should see following elements
- | /myFOLDER/myTMP/ |
-
- Scenario: Check quota of owners parent directory of a shared file
- Given using old dav path
- And As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user1" has a quota of "0"
- And User "user0" moved file "/welcome.txt" to "/myfile.txt"
- And file "myfile.txt" of user "user0" is shared with user "user1"
- When User "user1" uploads file "data/textfile.txt" to "/myfile.txt"
- Then the HTTP status code should be "204"
-
- Scenario: Don't allow sharing of the root
- Given user "user0" exists
- And As an "user0"
- When creating a share with
- | path | / |
- | shareType | 3 |
- Then the OCS status code should be "403"
-
- Scenario: Allow modification of reshare
- Given user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And user "user0" created a folder "/TMP"
- And file "TMP" of user "user0" is shared with user "user1"
- And file "TMP" of user "user1" is shared with user "user2"
- And As an "user1"
- When Updating last share with
- | permissions | 1 |
- Then the OCS status code should be "100"
-
- Scenario: Do not allow reshare to exceed permissions
- Given user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And user "user0" created a folder "/TMP"
- And As an "user0"
- And creating a share with
- | path | /TMP |
- | shareType | 0 |
- | shareWith | user1 |
- | permissions | 21 |
- And As an "user1"
- And creating a share with
- | path | /TMP |
- | shareType | 0 |
- | shareWith | user2 |
- | permissions | 21 |
- When Updating last share with
- | permissions | 31 |
- Then the OCS status code should be "404"
-
- Scenario: Only allow 1 link share per file/folder
- Given user "user0" exists
- And As an "user0"
- And creating a share with
- | path | welcome.txt |
- | shareType | 3 |
- When save last share id
- And creating a share with
- | path | welcome.txt |
- | shareType | 3 |
- Then share ids should match
-
- Scenario: Correct webdav share-permissions for owned file
- Given user "user0" exists
- And User "user0" uploads file with content "foo" to "/tmp.txt"
- When as "user0" gets properties of folder "/tmp.txt" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "19"
-
- Scenario: Correct webdav share-permissions for received file with edit and reshare permissions
- Given user "user0" exists
- And user "user1" exists
- And User "user0" uploads file with content "foo" to "/tmp.txt"
- And file "/tmp.txt" of user "user0" is shared with user "user1"
- When as "user1" gets properties of folder "/tmp.txt" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "19"
-
- Scenario: Correct webdav share-permissions for received file with edit permissions but no reshare permissions
- Given user "user0" exists
- And user "user1" exists
- And User "user0" uploads file with content "foo" to "/tmp.txt"
- And file "tmp.txt" of user "user0" is shared with user "user1"
- And As an "user0"
- And Updating last share with
- | permissions | 3 |
- When as "user1" gets properties of folder "/tmp.txt" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "3"
-
- Scenario: Correct webdav share-permissions for received file with reshare permissions but no edit permissions
- Given user "user0" exists
- And user "user1" exists
- And User "user0" uploads file with content "foo" to "/tmp.txt"
- And file "tmp.txt" of user "user0" is shared with user "user1"
- And As an "user0"
- And Updating last share with
- | permissions | 17 |
- When as "user1" gets properties of folder "/tmp.txt" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "17"
-
- Scenario: Correct webdav share-permissions for owned folder
- Given user "user0" exists
- And user "user0" created a folder "/tmp"
- When as "user0" gets properties of folder "/" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "31"
-
- Scenario: Correct webdav share-permissions for received folder with all permissions
- Given user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/tmp"
- And file "/tmp" of user "user0" is shared with user "user1"
- When as "user1" gets properties of folder "/tmp" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "31"
-
- Scenario: Correct webdav share-permissions for received folder with all permissions but edit
- Given user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/tmp"
- And file "/tmp" of user "user0" is shared with user "user1"
- And As an "user0"
- And Updating last share with
- | permissions | 29 |
- When as "user1" gets properties of folder "/tmp" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "29"
-
- Scenario: Correct webdav share-permissions for received folder with all permissions but create
- Given user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/tmp"
- And file "/tmp" of user "user0" is shared with user "user1"
- And As an "user0"
- And Updating last share with
- | permissions | 27 |
- When as "user1" gets properties of folder "/tmp" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "27"
-
- Scenario: Correct webdav share-permissions for received folder with all permissions but delete
- Given user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/tmp"
- And file "/tmp" of user "user0" is shared with user "user1"
- And As an "user0"
- And Updating last share with
- | permissions | 23 |
- When as "user1" gets properties of folder "/tmp" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "23"
-
- Scenario: Correct webdav share-permissions for received folder with all permissions but share
- Given user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/tmp"
- And file "/tmp" of user "user0" is shared with user "user1"
- And As an "user0"
- And Updating last share with
- | permissions | 15 |
- When as "user1" gets properties of folder "/tmp" with
- |{http://open-collaboration-services.org/ns}share-permissions |
- Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "15"
-
- Scenario: unique target names for incoming shares
- Given user "user0" exists
- And user "user1" exists
- And user "user2" exists
- And user "user0" created a folder "/foo"
- And user "user1" created a folder "/foo"
- When file "/foo" of user "user0" is shared with user "user2"
- And file "/foo" of user "user1" is shared with user "user2"
- Then user "user2" should see following elements
- | /foo/ |
- | /foo%20(2)/ |
-
- Scenario: Creating a new share with a disabled user
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And assure user "user0" is disabled
- And As an "user0"
- When sending "POST" to "/apps/files_sharing/api/v1/shares" with
- | path | welcome.txt |
- | shareWith | user1 |
- | shareType | 0 |
- Then the OCS status code should be "997"
- And the HTTP status code should be "401"
-
- Scenario: Deleting a group share as user
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And As an "user0"
- And creating a share with
- | path | welcome.txt |
- | shareType | 1 |
- | shareWith | group1 |
- When As an "user1"
- And Deleting last share
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
-
- Scenario: Merging shares for recipient when shared from outside with group and member
- Given using old dav path
- And As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And user "user0" created a folder "/merge-test-outside"
- When folder "/merge-test-outside" of user "user0" is shared with group "group1"
- And folder "/merge-test-outside" of user "user0" is shared with user "user1"
- Then as "user1" the folder "/merge-test-outside" exists
- And as "user1" the folder "/merge-test-outside (2)" does not exist
-
- Scenario: Merging shares for recipient when shared from outside with group and member with different permissions
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And user "user0" created a folder "/merge-test-outside-perms"
- When folder "/merge-test-outside-perms" of user "user0" is shared with group "group1" with permissions 1
- And folder "/merge-test-outside-perms" of user "user0" is shared with user "user1" with permissions 31
- Then as "user1" gets properties of folder "/merge-test-outside-perms" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
- And as "user1" the folder "/merge-test-outside-perms (2)" does not exist
-
- Scenario: Merging shares for recipient when shared from outside with two groups
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And group "group2" exists
- And user "user1" belongs to group "group1"
- And user "user1" belongs to group "group2"
- And user "user0" created a folder "/merge-test-outside-twogroups"
- When folder "/merge-test-outside-twogroups" of user "user0" is shared with group "group1"
- And folder "/merge-test-outside-twogroups" of user "user0" is shared with group "group2"
- Then as "user1" the folder "/merge-test-outside-twogroups" exists
- And as "user1" the folder "/merge-test-outside-twogroups (2)" does not exist
-
- Scenario: Merging shares for recipient when shared from outside with two groups with different permissions
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And group "group2" exists
- And user "user1" belongs to group "group1"
- And user "user1" belongs to group "group2"
- And user "user0" created a folder "/merge-test-outside-twogroups-perms"
- When folder "/merge-test-outside-twogroups-perms" of user "user0" is shared with group "group1" with permissions 1
- And folder "/merge-test-outside-twogroups-perms" of user "user0" is shared with group "group2" with permissions 31
- Then as "user1" gets properties of folder "/merge-test-outside-twogroups-perms" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
- And as "user1" the folder "/merge-test-outside-twogroups-perms (2)" does not exist
-
- Scenario: Merging shares for recipient when shared from outside with two groups and member
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And group "group2" exists
- And user "user1" belongs to group "group1"
- And user "user1" belongs to group "group2"
- And user "user0" created a folder "/merge-test-outside-twogroups-member-perms"
- When folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with group "group1" with permissions 1
- And folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with group "group2" with permissions 31
- And folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with user "user1" with permissions 1
- Then as "user1" gets properties of folder "/merge-test-outside-twogroups-member-perms" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
- And as "user1" the folder "/merge-test-outside-twogroups-member-perms (2)" does not exist
-
- Scenario: Merging shares for recipient when shared from inside with group
- Given As an "admin"
- And user "user0" exists
- And group "group1" exists
- And user "user0" belongs to group "group1"
- And user "user0" created a folder "/merge-test-inside-group"
- When folder "/merge-test-inside-group" of user "user0" is shared with group "group1"
- Then as "user0" the folder "/merge-test-inside-group" exists
- And as "user0" the folder "/merge-test-inside-group (2)" does not exist
-
- Scenario: Merging shares for recipient when shared from inside with two groups
- Given As an "admin"
- And user "user0" exists
- And group "group1" exists
- And group "group2" exists
- And user "user0" belongs to group "group1"
- And user "user0" belongs to group "group2"
- And user "user0" created a folder "/merge-test-inside-twogroups"
- When folder "/merge-test-inside-twogroups" of user "user0" is shared with group "group1"
- And folder "/merge-test-inside-twogroups" of user "user0" is shared with group "group2"
- Then as "user0" the folder "/merge-test-inside-twogroups" exists
- And as "user0" the folder "/merge-test-inside-twogroups (2)" does not exist
- And as "user0" the folder "/merge-test-inside-twogroups (3)" does not exist
-
- Scenario: Merging shares for recipient when shared from inside with group with less permissions
- Given As an "admin"
- And user "user0" exists
- And group "group1" exists
- And group "group2" exists
- And user "user0" belongs to group "group1"
- And user "user0" belongs to group "group2"
- And user "user0" created a folder "/merge-test-inside-twogroups-perms"
- When folder "/merge-test-inside-twogroups-perms" of user "user0" is shared with group "group1"
- And folder "/merge-test-inside-twogroups-perms" of user "user0" is shared with group "group2"
- Then as "user0" gets properties of folder "/merge-test-inside-twogroups-perms" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "RDNVCK"
- And as "user0" the folder "/merge-test-inside-twogroups-perms (2)" does not exist
- And as "user0" the folder "/merge-test-inside-twogroups-perms (3)" does not exist
-
- Scenario: Merging shares for recipient when shared from outside with group then user and recipient renames in between
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And user "user0" created a folder "/merge-test-outside-groups-renamebeforesecondshare"
- When folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with group "group1"
- And User "user1" moved folder "/merge-test-outside-groups-renamebeforesecondshare" to "/merge-test-outside-groups-renamebeforesecondshare-renamed"
- And Sleep for "1" seconds
- And folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with user "user1"
- Then as "user1" gets properties of folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
- And as "user1" the folder "/merge-test-outside-groups-renamebeforesecondshare" does not exist
-
- Scenario: Merging shares for recipient when shared from outside with user then group and recipient renames in between
- Given using old dav path
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "group1" exists
- And user "user1" belongs to group "group1"
- And user "user0" created a folder "/merge-test-outside-groups-renamebeforesecondshare"
- When folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with user "user1"
- And User "user1" moved folder "/merge-test-outside-groups-renamebeforesecondshare" to "/merge-test-outside-groups-renamebeforesecondshare-renamed"
- And Sleep for "1" seconds
- And folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with group "group1"
- Then as "user1" gets properties of folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" with
- |{http://owncloud.org/ns}permissions|
- And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
- And as "user1" the folder "/merge-test-outside-groups-renamebeforesecondshare" does not exist
-
- Scenario: Empting trashbin
- Given As an "admin"
- And user "user0" exists
- And User "user0" deletes file "/textfile0.txt"
- When User "user0" empties trashbin
- Then the HTTP status code should be "200"
-
- Scenario: orphaned shares
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/common"
- And user "user0" created a folder "/common/sub"
- And file "/common/sub" of user "user0" is shared with user "user1"
- And User "user0" deletes folder "/common"
- When User "user0" empties trashbin
- Then as "user1" the folder "/sub" does not exist
-
- Scenario: sharing again an own file while belonging to a group
- Given As an "admin"
- Given user "user0" exists
- And group "sharing-group" exists
- And user "user0" belongs to group "sharing-group"
- And file "welcome.txt" of user "user0" is shared with group "sharing-group"
- And Deleting last share
- When sending "POST" to "/apps/files_sharing/api/v1/shares" with
- | path | welcome.txt |
- | shareWith | sharing-group |
- | shareType | 1 |
- Then the OCS status code should be "100"
- And the HTTP status code should be "200"
-
- Scenario: unshare from self
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And group "sharing-group" exists
- And user "user0" belongs to group "sharing-group"
- And user "user1" belongs to group "sharing-group"
- And file "/PARENT/parent.txt" of user "user0" is shared with group "sharing-group"
- And user "user0" stores etag of element "/PARENT"
- And user "user1" stores etag of element "/"
- And As an "user1"
- When Deleting last share
- Then etag of element "/" of user "user1" has changed
- And etag of element "/PARENT" of user "user0" has not changed
-
- Scenario: do not allow to increase link share permissions on reshare
- Given As an "admin"
- And user "admin" created a folder "/TMP"
- And user "user0" exists
- And creating a share with
- | path | TMP |
- | shareType | 0 |
- | shareWith | user0 |
- | permissions | 17 |
- When As an "user0"
- And creating a share with
- | path | TMP |
- | shareType | 3 |
- And Updating last share with
- | publicUpload | true |
- Then the OCS status code should be "404"
-
- Scenario: moving a file into a share as recipient
- Given As an "admin"
- And user "user0" exists
- And user "user1" exists
- And user "user0" created a folder "/shared"
- And folder "/shared" of user "user0" is shared with user "user1"
- When User "user1" moved file "/textfile0.txt" to "/shared/shared_file.txt"
- Then as "user1" the file "/shared/shared_file.txt" exists
- And as "user0" the file "/shared/shared_file.txt" exists
+# See sharing-v1-part2.feature
projects / nextcloud-server.git / commitdiff