test DELETE requests on OCS endpoints as admin with invalid password

owncloud · Feb 28, 2019 · 6cfdd29 · 6cfdd29
1 parent 8ae223f
commit 6cfdd29
Showing 1 changed file with 28 additions and 0 deletions.
diff --git a/tests/acceptance/features/apiMain/auth.feature b/tests/acceptance/features/apiMain/auth.feature
@@ -231,6 +231,34 @@ Feature: auth
       | 1               |/cloud/users/user0/enable             | 997      | 401       |
       | 2               |/cloud/users/user0/enable             | 997      | 401       |
 
+  @issue-32068
+  Scenario Outline: send DELETE requests to OCS endpoints as admin with wrong password
+    Given using OCS API version "<ocs_api_version>"
+    And group "group1" has been created
+    When the administrator sends HTTP method "DELETE" to OCS API endpoint "<endpoint>" using password "invalid"
+    Then the OCS status code should be "<ocs-code>"
+    And the HTTP status code should be "<http-code>"
+    Examples:
+      | ocs_api_version |endpoint                                             | ocs-code | http-code |
+      | 1               |/apps/files_sharing/api/v1/remote_shares/pending/123 | 997      | 401       |
+      | 2               |/apps/files_sharing/api/v1/remote_shares/pending/123 | 997      | 401       |
+      | 1               |/apps/files_sharing/api/v1/remote_shares/123         | 997      | 401       |
+      | 2               |/apps/files_sharing/api/v1/remote_shares/123         | 997      | 401       |
+      | 1               |/apps/files_sharing/api/v1/shares/123                | 997      | 401       |
+      | 2               |/apps/files_sharing/api/v1/shares/123                | 997      | 401       |
+      | 1               |/apps/files_sharing/api/v1/shares/pending/123        | 997      | 401       |
+      | 2               |/apps/files_sharing/api/v1/shares/pending/123        | 997      | 401       |
+      | 1               |/cloud/apps/testing                                  | 997      | 401       |
+      | 2               |/cloud/apps/testing                                  | 997      | 401       |
+      | 1               |/cloud/groups/group1                                 | 997      | 401       |
+      | 2               |/cloud/groups/group1                                 | 997      | 401       |
+      | 1               |/cloud/users/user0                                   | 997      | 401       |
+      | 2               |/cloud/users/user0                                   | 997      | 401       |
+      | 1               |/cloud/users/user0/groups                            | 997      | 401       |
+      | 2               |/cloud/users/user0/groups                            | 997      | 401       |
+      | 1               |/cloud/users/user0/subadmins                         | 997      | 401       |
+      | 2               |/cloud/users/user0/subadmins                         | 997      | 401       |
+
   Scenario Outline: using OCS with token auth of a normal user
     When user "user0" requests "<endpoint>" with "GET" using basic token auth
     Then the OCS status code should be "<ocs-code>"