nextcloud-server/build/integration/sharing_features/sharing-v1-part2.feature

# SPDX-FileCopyrightText: 2019 Nextcloud GmbH and Nextcloud contributors
# SPDX-License-Identifier: AGPL-3.0-or-later
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 user "user1" accepts last share
    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: getting all shares of a file with a received share after revoking the resharing rights
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And file "textfile0.txt" of user "user1" is shared with user "user0"
    And user "user0" accepts last share
    And Updating last share with
      | permissions | 1 |
    And file "textfile0.txt" of user "user1" is shared with user "user2"
    When As an "user0"
    And sending "GET" to "/apps/files_sharing/api/v1/shares?reshares=true&path=/textfile0 (2).txt"
    Then the list of returned shares has 1 shares
    And share 0 is returned with
      | share_type             | 0 |
      | uid_owner              | user1 |
      | displayname_owner      | user1 |
      | path                   | /textfile0 (2).txt |
      | item_type              | file |
      | mimetype               | text/plain |
      | storage_id             | shared::/textfile0 (2).txt |
      | file_target            | /textfile0.txt |
      | share_with             | user2 |
      | share_with_displayname | user2 |

  Scenario: getting all shares of a file with a received share also reshared after revoking the resharing rights
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And file "textfile0.txt" of user "user1" is shared with user "user0"
    And user "user0" accepts last share
    And save the last share data as "textfile0.txt from user1"
    And file "textfile0 (2).txt" of user "user0" is shared with user "user3"
    And restore the last share data from "textfile0.txt from user1"
    And Updating last share with
      | permissions | 1 |
    And file "textfile0.txt" of user "user1" is shared with user "user2"
    When As an "user0"
    And sending "GET" to "/apps/files_sharing/api/v1/shares?reshares=true&path=/textfile0 (2).txt"
    Then the list of returned shares has 2 shares
    And share 0 is returned with
      | share_type             | 0 |
      | uid_owner              | user0 |
      | displayname_owner      | user0 |
      | uid_file_owner         | user1 |
      | displayname_file_owner | user1 |
      | path                   | /textfile0 (2).txt |
      | item_type              | file |
      | mimetype               | text/plain |
      | storage_id             | shared::/textfile0 (2).txt |
      | file_target            | /textfile0 (2).txt |
      | share_with             | user3 |
      | share_with_displayname | user3 |
    And share 1 is returned with
      | share_type             | 0 |
      | uid_owner              | user1 |
      | displayname_owner      | user1 |
      | path                   | /textfile0 (2).txt |
      | item_type              | file |
      | mimetype               | text/plain |
      | storage_id             | shared::/textfile0 (2).txt |
      | file_target            | /textfile0.txt |
      | share_with             | user2 |
      | share_with_displayname | user2 |

  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 user "user1" accepts last share
    And file "textfile0 (2).txt" of user "user1" is shared with user "user2"
    And user "user2" accepts last share
    And file "textfile0 (2).txt" of user "user2" is shared with user "user3"
    And user "user3" accepts last share
    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: getting share info of a group share
    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 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 | 1 |
      | share_with | group1 |
      | 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 | group1 |
      | displayname_owner | user0 |
      | mimetype          | text/plain |
    And As an "user1"
    And accepting last share
    And Getting info of last share
    And 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 |
      | share_with | group1 |
      | file_source | A_NUMBER |
      | file_target | /textfile0 (2).txt |
      | path | /textfile0 (2).txt |
      | permissions | 19 |
      | stime | A_NUMBER |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | shared::/textfile0 (2).txt |
      | file_parent | A_NUMBER |
      | share_with_displayname | group1 |
      | displayname_owner | user0 |
      | mimetype          | text/plain |

  Scenario: getting all shares including subfiles in a directory
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And file "PARENT/CHILD" of user "user0" is shared with user "user1"
    And file "PARENT/parent.txt" of user "user0" is shared with user "user2"
    When As an "user0"
    And sending "GET" to "/apps/files_sharing/api/v1/shares?subfiles=true&path=PARENT"
    Then the list of returned shares has 2 shares
    And share 0 is returned with
      | share_type             | 0 |
      | uid_owner              | user0 |
      | displayname_owner      | user0 |
      | path                   | /PARENT/CHILD |
      | item_type              | folder |
      | mimetype               | httpd/unix-directory |
      | storage_id             | home::user0 |
      | file_target            | /CHILD |
      | share_with             | user1 |
      | share_with_displayname | user1 |
      | permissions            | 31 |
    And share 1 is returned with
      | share_type             | 0 |
      | uid_owner              | user0 |
      | displayname_owner      | user0 |
      | path                   | /PARENT/parent.txt |
      | item_type              | file |
      | mimetype               | text/plain |
      | storage_id             | home::user0 |
      | file_target            | /parent.txt |
      | share_with             | user2 |
      | share_with_displayname | user2 |

  Scenario: getting all shares including subfiles in a directory with received shares
    Given user "user0" exists
    And user "user1" exists
    And file "textfile0.txt" of user "user0" is shared with user "user1"
    And user "user1" accepts last share
    And file "textfile0.txt" of user "user1" is shared with user "user0"
    When As an "user0"
    And sending "GET" to "/apps/files_sharing/api/v1/shares?subfiles=true&path=/"
    Then the list of returned shares has 1 shares
    And share 0 is returned with
      | share_type             | 0 |
      | uid_owner              | user0 |
      | displayname_owner      | user0 |
      | path                   | /textfile0.txt |
      | item_type              | file |
      | mimetype               | text/plain |
      | storage_id             | home::user0 |
      | file_target            | /textfile0 (2).txt |
      | share_with             | user1 |
      | share_with_displayname | user1 |

  Scenario: getting all shares including subfiles in a directory with shares in subdirectories
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And file "PARENT/CHILD" of user "user0" is shared with user "user1"
    And file "PARENT/CHILD/child.txt" of user "user0" is shared with user "user2"
    When As an "user0"
    And sending "GET" to "/apps/files_sharing/api/v1/shares?subfiles=true&path=PARENT"
    Then the list of returned shares has 1 shares
    And share 0 is returned with
      | share_type             | 0 |
      | uid_owner              | user0 |
      | displayname_owner      | user0 |
      | path                   | /PARENT/CHILD |
      | item_type              | folder |
      | mimetype               | httpd/unix-directory |
      | storage_id             | home::user0 |
      | file_target            | /CHILD |
      | share_with             | user1 |
      | share_with_displayname | user1 |
      | permissions            | 31 |

  Scenario: getting all shares including subfiles in a shared directory with reshares
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And file "PARENT" of user "user0" is shared with user "user1"
    And user "user1" accepts last share
    And file "PARENT (2)/CHILD" of user "user1" is shared with user "user2"
    And user "user2" accepts last share
    And file "CHILD" of user "user2" is shared with user "user3"
    When As an "user0"
    And sending "GET" to "/apps/files_sharing/api/v1/shares?subfiles=true&path=PARENT"
    Then the list of returned shares has 2 shares
    And share 0 is returned with
      | share_type             | 0 |
      | uid_owner              | user1 |
      | displayname_owner      | user1 |
      | uid_file_owner         | user0 |
      | displayname_file_owner | user0 |
      | path                   | /PARENT/CHILD |
      | item_type              | folder |
      | mimetype               | httpd/unix-directory |
      | storage_id             | home::user0 |
      | file_target            | /CHILD |
      | share_with             | user2 |
      | share_with_displayname | user2 |
      | permissions            | 31 |
    And share 1 is returned with
      | share_type             | 0 |
      | uid_owner              | user2 |
      | displayname_owner      | user2 |
      | uid_file_owner         | user0 |
      | displayname_file_owner | user0 |
      | path                   | /PARENT/CHILD |
      | item_type              | folder |
      | mimetype               | httpd/unix-directory |
      | storage_id             | home::user0 |
      | file_target            | /CHILD |
      | share_with             | user3 |
      | share_with_displayname | user3 |
      | permissions            | 31 |

  Scenario: getting all shares including subfiles in a directory by a resharer
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And file "PARENT" of user "user0" is shared with user "user1"
    And user "user1" accepts last share
    And file "PARENT (2)/CHILD" of user "user1" is shared with user "user2"
    And user "user2" accepts last share
    And file "CHILD" of user "user2" is shared with user "user3"
    When As an "user1"
    And sending "GET" to "/apps/files_sharing/api/v1/shares?subfiles=true&path=PARENT (2)"
    Then the list of returned shares has 2 shares
    And share 0 is returned with
      | share_type             | 0 |
      | uid_owner              | user1 |
      | displayname_owner      | user1 |
      | uid_file_owner         | user0 |
      | displayname_file_owner | user0 |
      | path                   | /PARENT (2)/CHILD |
      | item_type              | folder |
      | mimetype               | httpd/unix-directory |
      | storage_id             | shared::/PARENT (2) |
      | file_target            | /CHILD |
      | share_with             | user2 |
      | share_with_displayname | user2 |
      | permissions            | 31 |
    And share 1 is returned with
      | share_type             | 0 |
      | uid_owner              | user2 |
      | displayname_owner      | user2 |
      | uid_file_owner         | user0 |
      | displayname_file_owner | user0 |
      | path                   | /PARENT (2)/CHILD |
      | item_type              | folder |
      | mimetype               | httpd/unix-directory |
      | storage_id             | shared::/PARENT (2) |
      | file_target            | /CHILD |
      | share_with             | user3 |
      | share_with_displayname | user3 |
      | permissions            | 31 |

  Scenario: getting all shares including subfiles in a directory by a resharer after revoking the resharing rights
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And file "PARENT" of user "user0" is shared with user "user1"
    And save the last share data as "parent folder"
    And user "user1" accepts last share
    And file "PARENT (2)/CHILD" of user "user1" is shared with user "user2"
    And user "user2" accepts last share
    And file "CHILD" of user "user2" is shared with user "user3"
    And As an "user0"
    And restore the last share data from "parent folder"
    And Updating last share with
      | permissions | 1 |
    When As an "user1"
    And sending "GET" to "/apps/files_sharing/api/v1/shares?subfiles=true&path=PARENT (2)"
    Then the list of returned shares has 1 shares
    And share 0 is returned with
      | share_type             | 0 |
      | uid_owner              | user1 |
      | displayname_owner      | user1 |
      | uid_file_owner         | user0 |
      | displayname_file_owner | user0 |
      | path                   | /PARENT (2)/CHILD |
      | item_type              | folder |
      | mimetype               | httpd/unix-directory |
      | storage_id             | shared::/PARENT (2) |
      | file_target            | /CHILD |
      | share_with             | user2 |
      | share_with_displayname | user2 |
      | permissions            | 31 |

  Scenario: getting all shares including subfiles in a directory after moving a received share not reshareable also shared with another user
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And file "textfile0.txt" of user "user1" is shared with user "user0"
    And user "user0" accepts last share
    And Updating last share with
      | permissions | 1 |
    And file "textfile0.txt" of user "user1" is shared with user "user2"
    And User "user0" moved file "/textfile0 (2).txt" to "/FOLDER/textfile0.txt"
    When As an "user0"
    And sending "GET" to "/apps/files_sharing/api/v1/shares?subfiles=true&path=/FOLDER"
    Then the list of returned shares has 1 shares
    And share 0 is returned with
      | share_type             | 0 |
      | uid_owner              | user1 |
      | displayname_owner      | user1 |
      | path                   | /FOLDER/textfile0.txt |
      | item_type              | file |
      | mimetype               | text/plain |
      | storage_id             | shared::/FOLDER/textfile0.txt |
      | file_target            | /textfile0.txt |
      | share_with             | user2 |
      | share_with_displayname | user2 |

  Scenario: getting all shares including subfiles in a directory after moving a share and a received share not reshareable also shared with another user
    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 user "user1" accepts last share
    And file "textfile0.txt" of user "user1" is shared with user "user0"
    And user "user0" accepts last share
    And Updating last share with
      | permissions | 1 |
    And file "textfile0.txt" of user "user1" is shared with user "user2"
    And User "user0" moved file "/textfile0.txt" to "/FOLDER/textfile0.txt"
    And User "user0" moved file "/textfile0 (2).txt" to "/FOLDER/textfile0 (2).txt"
    When As an "user0"
    And sending "GET" to "/apps/files_sharing/api/v1/shares?subfiles=true&path=/FOLDER"
    Then the list of returned shares has 2 shares
    And share 0 is returned with
      | share_type             | 0 |
      | uid_owner              | user0 |
      | displayname_owner      | user0 |
      | path                   | /FOLDER/textfile0.txt |
      | item_type              | file |
      | mimetype               | text/plain |
      | storage_id             | home::user0 |
      | file_target            | /textfile0 (2).txt |
      | share_with             | user1 |
      | share_with_displayname | user1 |
    And share 1 is returned with
      | share_type             | 0 |
      | uid_owner              | user1 |
      | displayname_owner      | user1 |
      | path                   | /FOLDER/textfile0 (2).txt |
      | item_type              | file |
      | mimetype               | text/plain |
      | storage_id             | shared::/FOLDER/textfile0 (2).txt |
      | file_target            | /textfile0.txt |
      | share_with             | user2 |
      | share_with_displayname | user2 |

  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" accepts last share
    And User "user1" moved file "/textfile0 (2).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 |
    And As an "user1"
    And Getting info of last share
    And 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 | /FOLDER/textfile0.txt |
      | permissions | 1 |
      | stime | A_NUMBER |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | shared::/FOLDER/textfile0.txt |
      | 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 user "user1" accepts last share
    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 user "user1" accepts last share
    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"
    And accepting last share
    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 allowed to reshare file with more permissions if shares of same file to same user have them
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And group "group1" exists
    And user "user1" belongs to group "group1"
    And As an "user0"
    And creating a share with
      | path | /textfile0.txt |
      | shareType | 1 |
      | shareWith | group1 |
      | permissions | 15 |
    And As an "user1"
    And accepting last share
    And As an "user0"
    And creating a share with
      | path | /textfile0.txt |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 17 |
    And As an "user1"
    And accepting last share
    When creating a share with
      | path | /textfile0 (2).txt |
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 19 |
    Then the OCS status code should be "100"
    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"
    And accepting last share
    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 even if shares of same file to other users have them
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And As an "user0"
    And creating a share with
      | path | /textfile0.txt |
      | shareType | 0 |
      | shareWith | user3 |
      | permissions | 15 |
    And As an "user3"
    And accepting last share
    And As an "user0"
    And creating a share with
      | path | /textfile0.txt |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 17 |
    And As an "user1"
    And accepting last share
    When creating a share with
      | path | /textfile0 (2).txt |
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 19 |
    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 even if shares of other files from same user have them
    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 | 15 |
    And As an "user1"
    And accepting last share
    And As an "user0"
    And creating a share with
      | path | /textfile1.txt |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 17 |
    And As an "user1"
    And accepting last share
    When creating a share with
      | path | /textfile1 (2).txt |
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 19 |
    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 even if shares of other files from other users have them
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And As an "user3"
    And creating a share with
      | path | /textfile0.txt |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 15 |
    And As an "user1"
    And accepting last share
    And As an "user0"
    And creating a share with
      | path | /textfile1.txt |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 17 |
    And As an "user1"
    And accepting last share
    When creating a share with
      | path | /textfile1 (2).txt |
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 19 |
    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 additional delete 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 | /PARENT |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 16 |
    And As an "user1"
    And accepting last share
    When creating a share with
      | path | /PARENT (2) |
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 25 |
    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 additional delete permissions for files
  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"
    And accepting last share
    When creating a share with
      | path | /textfile0 (2).txt |
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 25 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    When Getting info of last share
    Then Share fields of last share match with
      | id | A_NUMBER |
      | item_type | file |
      | item_source | A_NUMBER |
      | share_type | 0 |
      | share_with | user2 |
      | file_source | A_NUMBER |
      | file_target | /textfile0 (2).txt |
      | path | /textfile0 (2).txt |
      | permissions | 17 |
      | stime | A_NUMBER |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user1 |
      | storage_id | shared::/textfile0 (2).txt |
      | file_parent | A_NUMBER |
      | share_with_displayname | user2 |
      | displayname_owner | user1 |
      | mimetype          | text/plain |

  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: Get a share with a user with resharing rights
    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 user "user1" accepts last share
    And file "textfile0.txt" of user "user0" is shared with user "user2"
    And As an "user1"
    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 | user2 |
      | file_source | A_NUMBER |
      | file_target | /textfile0.txt |
      | path | /textfile0 (2).txt |
      | permissions | 19 |
      | stime | A_NUMBER |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | shared::/textfile0 (2).txt |
      | file_parent | A_NUMBER |
      | share_with_displayname | user2 |
      | displayname_owner | user0 |
      | mimetype          | text/plain |

  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"
    And user "user1" accepts last share
    When file "/PARENT/CHILD" of user "user0" is shared with group "group0"
    And user "user1" accepts last share
    Then user "user1" should see following elements
      | /FOLDER/ |
      | /PARENT/ |
      | /PARENT/CHILD/ |
      | /PARENT/parent.txt |
      | /PARENT/CHILD/child.txt |
      | /PARENT%20(2)/ |
      | /PARENT%20(2)/CHILD/ |
      | /PARENT%20(2)/parent.txt |
      | /PARENT%20(2)/CHILD/child.txt |
      | /CHILD/ |
      | /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 user "user1" accepts last share
    And user "user2" accepts last share
    And file "textfile0.txt" of user "user1" is shared with user "user2"
    And user "user2" accepts last share
    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 user "user1" accepts last share
    And user "user2" accepts last share
    And file "textfile0.txt" of user "user1" is shared with user "user2"
    And user "user2" accepts last share
    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 (2).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" accepts last share
    And User "user1" moved file "/textfile0 (2).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: delete a share with a user that didn't receive 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 Deleting last share
    Then the OCS status code should be "404"
    And the HTTP status code should be "200"

  Scenario: delete a share with a user with resharing rights that didn't receive 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 user "user1" accepts last share
    And file "textfile0.txt" of user "user0" is shared with user "user2"
    And As an "user1"
    When Deleting last share
    Then the OCS status code should be "403"
    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" accepts last share
    And user "user2" accepts last share
    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"
    And user "user1" accepts last share
    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 user "user1" accepts last share
    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"
    And the HTTP status code should be "200"

  Scenario: Allow reshare to exceed permissions if shares of same file to same user have them
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And group "group1" exists
    And user "user1" belongs to group "group1"
    And user "user0" created a folder "/TMP"
    And As an "user0"
    And creating a share with
      | path | /TMP |
      | shareType | 1 |
      | shareWith | group1 |
      | permissions | 15 |
    And As an "user1"
    And accepting last share
    And As an "user0"
    And creating a share with
      | path | /TMP |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 17 |
    And As an "user1"
    And accepting last share
    And creating a share with
      | path | /TMP |
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 17 |
    When Updating last share with
      | permissions | 31 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"

  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 accepting last share
    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"
    And the HTTP status code should be "200"

  Scenario: Do not allow reshare to exceed permissions even if shares of same file to other users have them
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And user "user0" created a folder "/TMP"
    And As an "user0"
    And creating a share with
      | path | /TMP |
      | shareType | 0 |
      | shareWith | user3 |
      | permissions | 15 |
    And As an "user3"
    And accepting last share
    And As an "user0"
    And creating a share with
      | path | /TMP |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 21 |
    And As an "user1"
    And accepting last share
    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"
    And the HTTP status code should be "200"

  Scenario: Do not allow reshare to exceed permissions even if shares of other files from same user have them
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And As an "user0"
    And creating a share with
      | path | /FOLDER |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 15 |
    And As an "user1"
    And accepting last share
    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 accepting last share
    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"
    And the HTTP status code should be "200"

  Scenario: Do not allow reshare to exceed permissions even if shares of other files from other users have them
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And As an "user3"
    And creating a share with
      | path | /FOLDER |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 15 |
    And As an "user1"
    And accepting last share
    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 accepting last share
    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"
    And the HTTP status code should be "200"

  Scenario: Do not allow sub reshare to exceed permissions
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user0" created a folder "/TMP"
    And user "user0" created a folder "/TMP/SUB"
    And As an "user0"
    And creating a share with
      | path | /TMP |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 21 |
    And As an "user1"
    And accepting last share
    And creating a share with
      | path | /TMP/SUB |
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 21 |
    When Updating last share with
      | permissions | 31 |
    Then the OCS status code should be "404"
    And the HTTP status code should be "200"

  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: Cannot download a file when it's shared view-only
    Given user "user0" exists
    And user "user1" exists
    And User "user0" moves file "/textfile0.txt" to "/document.odt"
    And file "document.odt" of user "user0" is shared with user "user1" view-only
    And user "user1" accepts last share
    When As an "user1"
    And Downloading file "/document.odt"
    Then the HTTP status code should be "403"

  Scenario: Cannot download a file when its parent is shared view-only
    Given user "user0" exists
    And user "user1" exists
    And User "user0" created a folder "/sharedviewonly"
    And User "user0" moves file "/textfile0.txt" to "/sharedviewonly/document.odt"
    And folder "sharedviewonly" of user "user0" is shared with user "user1" view-only
    And user "user1" accepts last share
    When As an "user1"
    And Downloading file "/sharedviewonly/document.odt"
    Then the HTTP status code should be "403"

  Scenario: Cannot copy a file when it's shared view-only
    Given user "user0" exists
    And user "user1" exists
    And User "user0" moves file "/textfile0.txt" to "/document.odt"
    And file "document.odt" of user "user0" is shared with user "user1" view-only
    And user "user1" accepts last share
    When User "user1" copies file "/document.odt" to "/copyforbidden.odt"
    Then the HTTP status code should be "403"

  Scenario: Cannot copy a file when its parent is shared view-only
    Given user "user0" exists
    And user "user1" exists
    And User "user0" created a folder "/sharedviewonly"
    And User "user0" moves file "/textfile0.txt" to "/sharedviewonly/document.odt"
    And folder "sharedviewonly" of user "user0" is shared with user "user1" view-only
    And user "user1" accepts last share
    When User "user1" copies file "/sharedviewonly/document.odt" to "/copyforbidden.odt"
    Then the HTTP status code should be "403"

# See sharing-v1-part3.feature