sevenhill/QSfera
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #627 from butonic/add-basic-auth-option

Browse Source 
add enable basic auth option and check permissions
This commit is contained in:
Jörn Friedrich Dreyer
2020-11-05 16:36:16 +01:00
committed by GitHub
parent 681885d06e fdfd4040b7
commit c124102df2
50 changed files with 1530 additions and 2286 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ocis/tests/acceptance/expected-failures-on-OCIS-storage.txt
+5 -40
View File
@@ -202,18 +202,12 @@ apiProvisioning-v2/apiProvisioningUsingAppPassword.feature:67
# https://github.com/owncloud/ocis-ocs/issues/28
# disable users /cloud/users/disable|enable not available
#
apiProvisioning-v1/disableUser.feature:11
apiProvisioning-v1/disableUser.feature:79
apiProvisioning-v1/disableUser.feature:99
apiProvisioning-v1/disableUser.feature:107
apiProvisioning-v1/disableUser.feature:129
apiProvisioning-v1/enableUser.feature:11
apiProvisioning-v2/disableUser.feature:11
apiProvisioning-v2/disableUser.feature:79
apiProvisioning-v2/disableUser.feature:99
apiProvisioning-v2/disableUser.feature:108
apiProvisioning-v2/disableUser.feature:130
apiProvisioning-v2/enableUser.feature:11
#
# https://github.com/owncloud/ocis-ocs/issues/51
# displayname of user can be changed to empty
@@ -226,9 +220,6 @@ apiProvisioning-v2/editUser.feature:47
#
apiProvisioning-v1/editUser.feature:56
apiProvisioning-v1/editUser.feature:122
apiProvisioning-v1/enableUser.feature:34
apiProvisioning-v1/enableUser.feature:56
apiProvisioning-v1/enableUser.feature:63
apiProvisioning-v2/editUser.feature:56
apiProvisioning-v2/editUser.feature:122
apiProvisioning-v2/enableUser.feature:34
@@ -238,14 +229,10 @@ apiProvisioning-v2/enableUser.feature:64
# https://github.com/owncloud/product/issues/248
# user can get info of other users/ cloud/users endpoints not authenticated
#
apiProvisioning-v1/deleteUser.feature:53
apiProvisioning-v2/deleteUser.feature:54
apiProvisioning-v1/getUser.feature:81
apiProvisioning-v1/getUsers.feature:43
apiProvisioning-v1/resetUserPassword.feature:56
apiProvisioning-v2/getUser.feature:82
apiProvisioning-v2/getUsers.feature:44
apiProvisioning-v2/resetUserPassword.feature:56
#
# https://github.com/owncloud/product/issues/250
# incorrect ocs(v2) status value when getting info of user that does not exist should be 404, gives 998
@@ -315,7 +302,6 @@ apiSharees/sharees.feature:538
# https://github.com/owncloud/ocis-reva/issues/34 groups endpoint does not exist
#
apiShareManagementToShares/acceptShares.feature:22
apiShareManagementToShares/acceptShares.feature:52
apiShareManagementToShares/acceptShares.feature:71
apiShareManagementToShares/acceptShares.feature:156
apiShareManagementToShares/acceptShares.feature:157
@@ -331,12 +317,9 @@ apiShareManagementToShares/acceptShares.feature:249
apiShareManagementToShares/acceptShares.feature:270
apiShareManagementToShares/acceptShares.feature:279
apiShareManagementToShares/acceptShares.feature:298
apiShareManagementToShares/acceptShares.feature:320
apiShareManagementToShares/acceptShares.feature:342
apiShareManagementToShares/acceptShares.feature:378
apiShareManagementToShares/acceptShares.feature:398
apiShareManagementToShares/acceptShares.feature:417
apiShareManagementToShares/acceptShares.feature:439
#
# https://github.com/owncloud/product/issues/207 Response is empty when accepting a share
#
@@ -401,12 +384,8 @@ apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.fe
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:70
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:97
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:98
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:115
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:116
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:135
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:136
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:153
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:154
#
# https://github.com/owncloud/ocis/issues/720 shares are mounted into /Shares folder even after the sharer deletes the collaborator
# https://github.com/owncloud/ocis/issues/721 deleting share response does not contain `data` field
@@ -451,11 +430,6 @@ apiShareOperationsToShares/accessToShare.feature:56
apiShareOperationsToShares/gettingShares.feature:24
apiShareOperationsToShares/gettingShares.feature:25
#
# https://github.com/owncloud/ocis-reva/issues/65 There is no such thing like a "super-user"
#
apiShareOperationsToShares/gettingShares.feature:38
apiShareOperationsToShares/gettingShares.feature:39
#
# https://github.com/owncloud/ocis-reva/issues/357 Delete shares from user when user is deleted
# https://github.com/owncloud/ocis-reva/issues/301 no displayname_owner shown when creating a share
# https://github.com/owncloud/ocis-reva/issues/302 when sharing a file mime-type field is set to application/octet-stream
@@ -549,11 +523,8 @@ apiSharePublicLink1/changingPublicLinkShare.feature:96
#
apiSharePublicLink1/changingPublicLinkShare.feature:63
apiSharePublicLink1/changingPublicLinkShare.feature:107
apiSharePublicLink1/changingPublicLinkShare.feature:128
apiSharePublicLink1/changingPublicLinkShare.feature:151
apiSharePublicLink1/changingPublicLinkShare.feature:174
apiSharePublicLink1/changingPublicLinkShare.feature:197
apiSharePublicLink1/changingPublicLinkShare.feature:221
apiSharePublicLink1/changingPublicLinkShare.feature:244
#
# https://github.com/owncloud/ocis-reva/issues/292 Public link enforce permissions
@@ -708,6 +679,11 @@ apiSharePublicLink2/uploadToPublicLinkShare.feature:103
apiSharePublicLink2/uploadToPublicLinkShare.feature:121
apiSharePublicLink2/uploadToPublicLinkShare.feature:139
#
# https://github.com/owncloud/ocis/issues/801 deleting a folder should delete share links to it as well
#
apiSharePublicLink2/uploadToPublicLinkShare.feature:48
apiSharePublicLink2/uploadToPublicLinkShare.feature:49
#
# https://github.com/owncloud/ocis-reva/issues/286 Upload-only shares must not overwrite but create a separate file
#
apiSharePublicLink2/uploadToPublicLinkShare.feature:23
@@ -1190,8 +1166,6 @@ apiWebdavOperations/downloadFile.feature:84
apiWebdavOperations/downloadFile.feature:85
apiWebdavOperations/refuseAccess.feature:21
apiWebdavOperations/refuseAccess.feature:22
apiWebdavOperations/refuseAccess.feature:33
apiWebdavOperations/refuseAccess.feature:34
#
# https://github.com/owncloud/core/pull/38035 PROPFIND to https://localhost:9200/remote.php/dav/files gets an error 500 response
#
@@ -1535,15 +1509,6 @@ apiWebdavPreviews/previews.feature:166
apiWebdavPreviews/previews.feature:178
apiWebdavPreviews/previews.feature:179
#
# https://github.com/owncloud/ocis-ocs/issues/35 group support is not yet implemented
#
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:93
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:94
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:114
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:115
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:116
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:117
#
# https://github.com/owncloud/product/issues/241 deleting an item updates etags of grandparent but not on parent
#
apiWebdavEtagPropagation1/deleteFileFolder.feature:25
ocis/tests/acceptance/expected-failures-on-OWNCLOUD-storage.txt
+5 -52
View File
@@ -172,24 +172,12 @@ apiProvisioning-v2/enableUser.feature:32
apiProvisioning-v2/getUser.feature:34
apiProvisioning-v2/getUser.feature:35
#
# https://github.com/owncloud/ocis-accounts/issues/80
# Creating an already existing user works
#
apiProvisioning-v1/addUser.feature:32
apiProvisioning-v1/addUser.feature:39
apiProvisioning-v2/addUser.feature:39
#
# https://github.com/owncloud/product/issues/197
# Password can be set to empty
#
apiProvisioning-v1/addUser.feature:69
apiProvisioning-v2/addUser.feature:69
#
# https://github.com/owncloud/ocis-accounts/issues/128
# Username is case sensitive
#
apiProvisioning-v1/addUser.feature:102
#
# https://github.com/owncloud/ocis/issues/197
# Client token generation not implemented
#
@@ -201,18 +189,12 @@ apiProvisioning-v2/apiProvisioningUsingAppPassword.feature:67
# https://github.com/owncloud/ocis-ocs/issues/28
# disable users /cloud/users/disable|enable not available
#
apiProvisioning-v1/disableUser.feature:11
apiProvisioning-v1/disableUser.feature:79
apiProvisioning-v1/disableUser.feature:99
apiProvisioning-v1/disableUser.feature:107
apiProvisioning-v1/disableUser.feature:129
apiProvisioning-v1/enableUser.feature:11
apiProvisioning-v2/disableUser.feature:11
apiProvisioning-v2/disableUser.feature:79
apiProvisioning-v2/disableUser.feature:99
apiProvisioning-v2/disableUser.feature:108
apiProvisioning-v2/disableUser.feature:130
apiProvisioning-v2/enableUser.feature:11
#
# https://github.com/owncloud/ocis-ocs/issues/51
# displayname of user can be changed to empty
@@ -225,9 +207,6 @@ apiProvisioning-v2/editUser.feature:47
#
apiProvisioning-v1/editUser.feature:56
apiProvisioning-v1/editUser.feature:122
apiProvisioning-v1/enableUser.feature:34
apiProvisioning-v1/enableUser.feature:56
apiProvisioning-v1/enableUser.feature:63
apiProvisioning-v2/editUser.feature:56
apiProvisioning-v2/editUser.feature:122
apiProvisioning-v2/enableUser.feature:34
@@ -237,14 +216,10 @@ apiProvisioning-v2/enableUser.feature:64
# https://github.com/owncloud/product/issues/248
# user can get info of other users/ cloud/users endpoints not authenticated
#
apiProvisioning-v1/deleteUser.feature:53
apiProvisioning-v2/deleteUser.feature:54
apiProvisioning-v1/getUser.feature:81
apiProvisioning-v1/getUsers.feature:43
apiProvisioning-v1/resetUserPassword.feature:56
apiProvisioning-v2/getUser.feature:82
apiProvisioning-v2/getUsers.feature:44
apiProvisioning-v2/resetUserPassword.feature:56
#
# https://github.com/owncloud/product/issues/250
# incorrect ocs(v2) status value when getting info of user that does not exist should be 404, gives 998
@@ -314,7 +289,6 @@ apiSharees/sharees.feature:538
# https://github.com/owncloud/ocis-reva/issues/34 groups endpoint does not exist
#
apiShareManagementToShares/acceptShares.feature:22
apiShareManagementToShares/acceptShares.feature:52
apiShareManagementToShares/acceptShares.feature:71
apiShareManagementToShares/acceptShares.feature:156
apiShareManagementToShares/acceptShares.feature:157
@@ -330,12 +304,9 @@ apiShareManagementToShares/acceptShares.feature:249
apiShareManagementToShares/acceptShares.feature:270
apiShareManagementToShares/acceptShares.feature:279
apiShareManagementToShares/acceptShares.feature:298
apiShareManagementToShares/acceptShares.feature:320
apiShareManagementToShares/acceptShares.feature:342
apiShareManagementToShares/acceptShares.feature:378
apiShareManagementToShares/acceptShares.feature:398
apiShareManagementToShares/acceptShares.feature:417
apiShareManagementToShares/acceptShares.feature:439
#
# https://github.com/owncloud/product/issues/207 Response is empty when accepting a share
#
@@ -400,12 +371,8 @@ apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.fe
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:70
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:97
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:98
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:115
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:116
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:135
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:136
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:153
apiShareManagementBasicToShares/excludeGroupFromReceivingSharesToSharesFolder.feature:154
#
# https://github.com/owncloud/ocis/issues/720 shares are mounted into /Shares folder even after the sharer deletes the collaborator
# https://github.com/owncloud/ocis/issues/721 deleting share response does not contain `data` field
@@ -443,11 +410,6 @@ apiShareOperationsToShares/accessToShare.feature:56
apiShareOperationsToShares/gettingShares.feature:24
apiShareOperationsToShares/gettingShares.feature:25
#
# https://github.com/owncloud/ocis-reva/issues/65 There is no such thing like a "super-user"
#
apiShareOperationsToShares/gettingShares.feature:38
apiShareOperationsToShares/gettingShares.feature:39
#
# https://github.com/owncloud/ocis-reva/issues/357 Delete shares from user when user is deleted
# https://github.com/owncloud/ocis-reva/issues/301 no displayname_owner shown when creating a share
# https://github.com/owncloud/ocis-reva/issues/302 when sharing a file mime-type field is set to application/octet-stream
@@ -526,11 +488,8 @@ apiSharePublicLink1/changingPublicLinkShare.feature:96
#
apiSharePublicLink1/changingPublicLinkShare.feature:63
apiSharePublicLink1/changingPublicLinkShare.feature:107
apiSharePublicLink1/changingPublicLinkShare.feature:128
apiSharePublicLink1/changingPublicLinkShare.feature:151
apiSharePublicLink1/changingPublicLinkShare.feature:174
apiSharePublicLink1/changingPublicLinkShare.feature:197
apiSharePublicLink1/changingPublicLinkShare.feature:221
apiSharePublicLink1/changingPublicLinkShare.feature:244
#
# https://github.com/owncloud/ocis-reva/issues/292 Public link enforce permissions
@@ -690,6 +649,11 @@ apiSharePublicLink2/uploadToPublicLinkShare.feature:103
apiSharePublicLink2/uploadToPublicLinkShare.feature:121
apiSharePublicLink2/uploadToPublicLinkShare.feature:139
#
# https://github.com/owncloud/ocis/issues/801 deleting a folder should delete share links to it as well
#
apiSharePublicLink2/uploadToPublicLinkShare.feature:48
apiSharePublicLink2/uploadToPublicLinkShare.feature:49
#
# https://github.com/owncloud/ocis-reva/issues/286 Upload-only shares must not overwrite but create a separate file
#
apiSharePublicLink2/uploadToPublicLinkShare.feature:23
@@ -1175,8 +1139,6 @@ apiWebdavOperations/downloadFile.feature:84
apiWebdavOperations/downloadFile.feature:85
apiWebdavOperations/refuseAccess.feature:21
apiWebdavOperations/refuseAccess.feature:22
apiWebdavOperations/refuseAccess.feature:33
apiWebdavOperations/refuseAccess.feature:34
#
# https://github.com/owncloud/core/pull/38035 PROPFIND to https://localhost:9200/remote.php/dav/files gets an error 500 response
#
@@ -1492,15 +1454,6 @@ apiWebdavPreviews/previews.feature:166
apiWebdavPreviews/previews.feature:178
apiWebdavPreviews/previews.feature:179
#
# https://github.com/owncloud/ocis-ocs/issues/35 group support is not yet implemented
#
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:93
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:94
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:114
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:115
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:116
apiShareCreateSpecialToShares2/createShareWithInvalidPermissions.feature:117
#
# https://github.com/owncloud/ocis/issues/762 path and other information are not shown if a share does not have "read" permission
#
apiShareOperationsToShares/uploadToShare.feature:64
ocis/tests/acceptance/features/apiOcisSpecific/apiAuthOcs-ocsDELETEAuth.feature
+7 -30
View File
@@ -3,6 +3,7 @@
Feature: auth
# these endpoints are handled by the reva ocs implementation
Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint |
@@ -20,39 +21,15 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "notset"
# these endpoints are handled by the ocis ocs implementation
Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v1.php/cloud/users/%username% |
| /ocs/v1.php/cloud/users/%username%/subadmins |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "998"
Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users/%username% |
Then the HTTP status code of responses on all endpoints should be "404"
And the OCS status code of responses on all endpoints should be "998"
Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v1.php/cloud/users/%username%/groups |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "996"
Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users/%username%/groups |
Then the HTTP status code of responses on all endpoints should be "500"
And the OCS status code of responses on all endpoints should be "996"
Scenario: send DELETE requests to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users/%username% |
| /ocs/v1.php/cloud/users/%username%/subadmins |
| /ocs/v2.php/cloud/users/%username%/subadmins |
Then the HTTP status code of responses on all endpoints should be "404"
And the OCS status code of responses on all endpoints should be "998"
| /ocs/v1.php/cloud/users/%username%/groups |
| /ocs/v2.php/cloud/users/%username%/groups |
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "notset"
ocis/tests/acceptance/features/apiOcisSpecific/apiAuthOcs-ocsGETAuth.feature
+18 -34
View File
@@ -20,8 +20,6 @@ Feature: auth
| /ocs/v2.php/apps/files_sharing/api/v1/shares |
| /ocs/v1.php/cloud/apps |
| /ocs/v2.php/cloud/apps |
| /ocs/v1.php/cloud/groups |
| /ocs/v2.php/cloud/groups |
| /ocs/v1.php/config |
| /ocs/v2.php/config |
| /ocs/v1.php/privatedata/getattribute |
@@ -33,15 +31,13 @@ Feature: auth
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: using OCS anonymously
When a user requests these endpoints with "GET" and no authentication
| endpoint |
| /ocs/v1.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "100"
When a user requests these endpoints with "GET" and no authentication
| endpoint |
| /ocs/v2.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "200"
| endpoint |
| /ocs/v1.php/cloud/users |
| /ocs/v2.php/cloud/users |
| /ocs/v1.php/cloud/groups |
| /ocs/v2.php/cloud/groups |
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "997"
@issue-ocis-reva-11
@@ -59,7 +55,6 @@ Feature: auth
| /ocs/v1.php/apps/files_sharing/api/v1/remote_shares |
| /ocs/v1.php/apps/files_sharing/api/v1/remote_shares/pending |
| /ocs/v1.php/privatedata/getattribute |
| /ocs/v1.php/cloud/groups |
| /ocs/v1.php/cloud/apps |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "998"
@@ -77,20 +72,17 @@ Feature: auth
# | /ocs/v2.php/apps/files_sharing/api/v1/shares | 100 | 200 |
| /ocs/v2.php/cloud/apps |
| /ocs/v2.php/cloud/groups |
| /ocs/v2.php/privatedata/getattribute |
Then the HTTP status code of responses on all endpoints should be "404"
And the OCS status code of responses on all endpoints should be "998"
When the user "Alice" requests these endpoints with "GET" with basic auth
| endpoint |
| /ocs/v1.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "100"
When the user "Alice" requests these endpoints with "GET" with basic auth
| endpoint |
| /ocs/v2.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "200"
| endpoint |
| /ocs/v1.php/cloud/users |
| /ocs/v2.php/cloud/users |
| /ocs/v1.php/cloud/groups |
| /ocs/v2.php/cloud/groups |
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "997"
When the user "Alice" requests these endpoints with "GET" with basic auth
| endpoint |
| /ocs/v2.php/config |
@@ -133,13 +125,9 @@ Feature: auth
When user "Alice" requests these endpoints with "GET" using password "invalid"
| endpoint |
| /ocs/v1.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "100"
When user "Alice" requests these endpoints with "GET" using password "invalid"
| endpoint |
| /ocs/v2.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "200"
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "notset"
@skipOnOcV10
@issue-ocis-reva-29
@@ -183,10 +171,6 @@ Feature: auth
When user "brian" requests these endpoints with "GET" using password "invalid"
| endpoint |
| /ocs/v1.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "100"
When user "brian" requests these endpoints with "GET" using password "invalid"
| endpoint |
| /ocs/v2.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "200"
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "notset"
ocis/tests/acceptance/features/apiOcisSpecific/apiAuthOcs-ocsPOSTAuth.feature
+6 -33
View File
@@ -28,43 +28,16 @@ Feature: auth
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "notset"
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: send POST requests to OCS endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v1.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "400"
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users |
Then the HTTP status code of responses on all endpoints should be "400"
And the OCS status code of responses on all endpoints should be "400"
@issue-ocis-reva-30
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: send POST requests to OCS endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v1.php/cloud/users/%username%/groups |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "400"
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users/%username%/groups |
Then the HTTP status code of responses on all endpoints should be "400"
And the OCS status code of responses on all endpoints should be "400"
@issue-ocis-reva-30
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: send POST requests to OCS endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v1.php/cloud/users |
| /ocs/v2.php/cloud/users |
| /ocs/v1.php/cloud/users/%username%/groups |
| /ocs/v2.php/cloud/users/%username%/groups |
| /ocs/v1.php/cloud/users/%username%/subadmins |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "998"
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users/%username%/subadmins |
Then the HTTP status code of responses on all endpoints should be "404"
And the OCS status code of responses on all endpoints should be "998"
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "notset"
ocis/tests/acceptance/features/apiOcisSpecific/apiAuthOcs-ocsPUTAuth.feature
+5 -22
View File
@@ -9,24 +9,11 @@ Feature: auth
| endpoint |
| /ocs/v1.php/apps/files_sharing/api/v1/shares/123 |
| /ocs/v2.php/apps/files_sharing/api/v1/shares/123 |
| /ocs/v1.php/cloud/users/%username% |
| /ocs/v2.php/cloud/users/%username% |
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "notset"
@issue-ocis-reva-30
@issue-ocis-ocs-26
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario: send PUT request to OCS endpoints as admin with wrong password
When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v1.php/cloud/users/%username% |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "998"
When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users/%username% |
Then the HTTP status code of responses on all endpoints should be "404"
And the OCS status code of responses on all endpoints should be "998"
@issue-ocis-reva-30
@issue-ocis-ocs-28
# after fixing all issues delete this Scenario and use the one from oC10 core
@@ -34,13 +21,9 @@ Feature: auth
When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v1.php/cloud/users/%username%/disable |
| /ocs/v1.php/cloud/users/%username%/enable |
Then the HTTP status code of responses on all endpoints should be "200"
And the OCS status code of responses on all endpoints should be "998"
When the administrator requests these endpoints with "PUT" with body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
| /ocs/v2.php/cloud/users/%username%/disable |
| /ocs/v1.php/cloud/users/%username%/enable |
| /ocs/v2.php/cloud/users/%username%/enable |
Then the HTTP status code of responses on all endpoints should be "404"
And the OCS status code of responses on all endpoints should be "998"
Then the HTTP status code of responses on all endpoints should be "401"
And the OCS status code of responses on all endpoints should be "notset"
ocis/tests/acceptance/features/apiOcisSpecific/apiSharePublicLink2-uploadToPublicLinkShare.feature
+16
View File
@@ -15,3 +15,19 @@ Feature: upload to a public link share
When user "Alice" deletes file "/FOLDER" using the WebDAV API
And the public uploads file "does-not-matter.txt" with content "does not matter" using the new public WebDAV API
Then the HTTP status code should be "500"
@issue-ocis-801
# after fixing all issues delete this Scenario and use the one from oC10 core
Scenario Outline: Uploading file to a public upload-only share using old public API that was deleted does not work
Given using <dav-path> DAV path
And user "Alice" has created a public link share with settings
| path | FOLDER |
| permissions | create |
When user "Alice" deletes file "/FOLDER" using the WebDAV API
Then uploading a file should not work using the old public WebDAV API
And the HTTP status code should be "401"
Examples:
| dav-path |
| old |
| new |