running secure viewer role with ocis wrapper instead of running ocis with GRAPH_AVAILABLE_ROLES
This commit is contained in:
@@ -88,9 +88,10 @@ Feature: sharing
|
||||
| dav-path | dav-path-personal |
|
||||
| /dav/spaces/%shares_drive_id% | /dav/spaces/%spaceid% |
|
||||
|
||||
@issue-8242 @issue-10334
|
||||
@issue-8242 @issue-10334 @env-config
|
||||
Scenario Outline: share receiver renames the shared item (old/new webdav)
|
||||
Given user "Alice" has uploaded file with content "foo" to "/sharefile.txt"
|
||||
And the administrator has enabled the permissions role "Secure Viewer"
|
||||
And using <dav-path-version> DAV path
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | sharefile.txt |
|
||||
@@ -126,13 +127,14 @@ Feature: sharing
|
||||
Examples:
|
||||
| dav-path-version | dav-path | permissions-role |
|
||||
| old | /webdav | Viewer |
|
||||
| old | /webdav | Secure viewer |
|
||||
| old | /webdav | Secure Viewer |
|
||||
| new | /dav/files/%username% | Viewer |
|
||||
| new | /dav/files/%username% | Secure viewer |
|
||||
| new | /dav/files/%username% | Secure Viewer |
|
||||
|
||||
@issue-8242
|
||||
@issue-8242 @env-config
|
||||
Scenario Outline: share receiver renames the shared item (spaces webdav)
|
||||
Given user "Alice" has uploaded file with content "foo" to "/sharefile.txt"
|
||||
And the administrator has enabled the permissions role "Secure Viewer"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
| resource | sharefile.txt |
|
||||
| space | Personal |
|
||||
@@ -168,7 +170,7 @@ Feature: sharing
|
||||
Examples:
|
||||
| dav-path | dav-path-personal | permissions-role |
|
||||
| /dav/spaces/%shares_drive_id% | /dav/spaces/%spaceid% | Viewer |
|
||||
| /dav/spaces/%shares_drive_id% | /dav/spaces/%spaceid% | Secure viewer |
|
||||
| /dav/spaces/%shares_drive_id% | /dav/spaces/%spaceid% | Secure Viewer |
|
||||
|
||||
|
||||
Scenario: keep group share when the one user renames the share and the user is deleted
|
||||
@@ -209,9 +211,10 @@ Feature: sharing
|
||||
And as "Alice" file "/folderToShare/renamedFile" should exist
|
||||
But as "Alice" file "/folderToShare/fileInside" should not exist
|
||||
|
||||
|
||||
@env-config
|
||||
Scenario Outline: receiver tries to rename a received share with read permissions inside the Shares folder
|
||||
Given user "Alice" has created folder "folderToShare"
|
||||
And the administrator has enabled the permissions role "Secure Viewer"
|
||||
And user "Alice" has created folder "folderToShare/folderInside"
|
||||
And user "Alice" has uploaded file with content "thisIsAFileInsideTheSharedFolder" to "/folderToShare/fileInside"
|
||||
And user "Alice" has sent the following resource share invitation:
|
||||
@@ -236,7 +239,7 @@ Feature: sharing
|
||||
Examples:
|
||||
| permissions-role |
|
||||
| Viewer |
|
||||
| Secure viewer |
|
||||
| Secure Viewer |
|
||||
|
||||
|
||||
Scenario: receiver renames a received folder share to a different name on the same folder
|
||||
|
||||
Reference in New Issue
Block a user