mirror of
https://github.com/opencloud-eu/opencloud.git
synced 2026-05-05 11:00:12 -05:00
check secure view permissions in the Report response
This commit is contained in:
@@ -56,7 +56,7 @@ Feature: REPORT request to Shares space
|
||||
| d:getcontenttype | text/plain |
|
||||
| oc:permissions | S |
|
||||
| d:getcontentlength | 34 |
|
||||
| oc:remote-item-id | UUIDof:folderMain |
|
||||
| oc:remote-item-id | UUIDof:folderMain |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
@@ -82,3 +82,70 @@ Feature: REPORT request to Shares space
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
|
||||
@issue-9607
|
||||
Scenario Outline: check the REPORT response of a folder shared with secure viewer role
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has created folder "/secureFolder"
|
||||
And user "Alice" has uploaded file with content "secure content" to "/secureFolder/secure.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | secureFolder |
|
||||
| space | Personal |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Secure viewer |
|
||||
When user "Brian" searches for "secureFolder" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the following headers should match these regular expressions
|
||||
| X-Request-Id | /^[a-zA-Z]+\/[a-zA-Z]+\.feature:\d+(-\d+)?$/ |
|
||||
And the "REPORT" response to user "Brian" should contain a mountpoint "secureFolder" with these key and value pairs:
|
||||
| key | value |
|
||||
| oc:shareroot | /secureFolder |
|
||||
| oc:name | secureFolder |
|
||||
| d:getcontenttype | httpd/unix-directory |
|
||||
| oc:permissions | SMX |
|
||||
| oc:size | 14 |
|
||||
| oc:remote-item-id | UUIDof:secureFolder |
|
||||
When user "Brian" searches for "secure.txt" using the WebDAV API
|
||||
And the following headers should match these regular expressions
|
||||
| X-Request-Id | /^[a-zA-Z]+\/[a-zA-Z]+\.feature:\d+(-\d+)?$/ |
|
||||
Then the HTTP status code should be "207"
|
||||
And the "REPORT" response to user "Brian" should contain a mountpoint "secureFolder" with these key and value pairs:
|
||||
| key | value |
|
||||
| oc:shareroot | /secureFolder |
|
||||
| oc:name | secure.txt |
|
||||
| d:getcontenttype | text/plain |
|
||||
| oc:permissions | SX |
|
||||
| d:getcontentlength | 14 |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
@issue-9607
|
||||
Scenario Outline: check the REPORT response of a file shared with secure viewer role
|
||||
Given using <dav-path-version> DAV path
|
||||
And user "Alice" has uploaded file with content "secure content" to "/secure.txt"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | secure.txt |
|
||||
| space | Personal |
|
||||
| sharee | Brian |
|
||||
| shareType | user |
|
||||
| permissionsRole | Secure viewer |
|
||||
When user "Brian" searches for "secure.txt" using the WebDAV API
|
||||
Then the HTTP status code should be "207"
|
||||
And the following headers should match these regular expressions
|
||||
| X-Request-Id | /^[a-zA-Z]+\/[a-zA-Z]+\.feature:\d+(-\d+)?$/ |
|
||||
And the "REPORT" response to user "Brian" should contain a mountpoint "secure.txt" with these key and value pairs:
|
||||
| key | value |
|
||||
| oc:shareroot | /secure.txt |
|
||||
| oc:name | secure.txt |
|
||||
| d:getcontenttype | text/plain |
|
||||
| oc:permissions | SMX |
|
||||
| d:getcontentlength | 14 |
|
||||
Examples:
|
||||
| dav-path-version |
|
||||
| old |
|
||||
| new |
|
||||
| spaces |
|
||||
|
||||
Reference in New Issue
Block a user