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

Remove brute-force-tag

Browse Source
This commit is contained in:
amrita
2023-05-04 12:42:14 +05:45
parent 73c327bdf0
commit 6ff7dc2741
13 changed files with 57 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/acceptance/features/coreApiAuthWebDav/webDavCOPYAuth.feature
+6 -6
View File
@@ -14,7 +14,7 @@ Feature: COPY file/folder
And user "Alice" has created folder "/FOLDER"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send COPY requests to webDav endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "COPY" using password "invalid" about user "Alice"
| endpoint |
@@ -25,7 +25,7 @@ Feature: COPY file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send COPY requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
When user "Alice" requests these endpoints with "COPY" using password "invalid" about user "Alice"
| endpoint |
@@ -34,7 +34,7 @@ Feature: COPY file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send COPY requests to webDav endpoints as normal user with no password
When user "Alice" requests these endpoints with "COPY" using password "" about user "Alice"
| endpoint |
@@ -45,7 +45,7 @@ Feature: COPY file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send COPY requests to webDav endpoints as normal user with no password using the spaces WebDAV API
When user "Alice" requests these endpoints with "COPY" using password "" about user "Alice"
| endpoint |
@@ -112,7 +112,7 @@ Feature: COPY file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send COPY requests to webDav endpoints without any authentication
When a user requests these endpoints with "COPY" with no authentication about user "Alice"
| endpoint |
@@ -123,7 +123,7 @@ Feature: COPY file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send COPY requests to webDav endpoints without any authentication using the spaces WebDAV API
When a user requests these endpoints with "COPY" with no authentication about user "Alice"
| endpoint |
tests/acceptance/features/coreApiAuthWebDav/webDavDELETEAuth.feature
+4 -4
View File
@@ -15,7 +15,7 @@ Feature: delete file/folder
And user "Alice" has created folder "/FOLDER"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send DELETE requests to webDav endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint |
@@ -27,7 +27,7 @@ Feature: delete file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send DELETE requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
When user "Alice" requests these endpoints with "DELETE" using password "invalid" about user "Alice"
| endpoint |
@@ -115,7 +115,7 @@ Feature: delete file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send DELETE requests to webDav endpoints without any authentication
When a user requests these endpoints with "DELETE" with no authentication about user "Alice"
| endpoint |
@@ -126,7 +126,7 @@ Feature: delete file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send DELETE requests to webDav endpoints without any authentication using the spaces WebDAV API
When a user requests these endpoints with "DELETE" with no authentication about user "Alice"
| endpoint |
tests/acceptance/features/coreApiAuthWebDav/webDavLOCKAuth.feature
+6 -6
View File
@@ -15,7 +15,7 @@ Feature: LOCK file/folder
And user "Alice" has created folder "/FOLDER"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send LOCK requests to webDav endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "LOCK" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
@@ -26,7 +26,7 @@ Feature: LOCK file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send LOCK requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
When user "Alice" requests these endpoints with "LOCK" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
@@ -35,7 +35,7 @@ Feature: LOCK file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send LOCK requests to webDav endpoints as normal user with no password
When user "Alice" requests these endpoints with "LOCK" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -46,7 +46,7 @@ Feature: LOCK file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send LOCK requests to webDav endpoints as normal user with no password using the spaces WebDAV API
When user "Alice" requests these endpoints with "LOCK" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -119,7 +119,7 @@ Feature: LOCK file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send LOCK requests to webDav endpoints without any authentication
When a user requests these endpoints with "LOCK" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
@@ -130,7 +130,7 @@ Feature: LOCK file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send LOCK requests to webDav endpoints without any authentication using the spaces WebDAV API
When a user requests these endpoints with "LOCK" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
tests/acceptance/features/coreApiAuthWebDav/webDavMKCOLAuth.feature
+6 -6
View File
@@ -11,7 +11,7 @@ Feature: create folder using MKCOL
And user "Alice" has created folder "/FOLDER"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send MKCOL requests to webDav endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "MKCOL" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
@@ -22,7 +22,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send MKCOL requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
When user "Alice" requests these endpoints with "MKCOL" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
@@ -31,7 +31,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send MKCOL requests to webDav endpoints as normal user with no password
When user "Alice" requests these endpoints with "MKCOL" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -42,7 +42,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @personalSpace @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest @personalSpace
Scenario: send MKCOL requests to webDav endpoints as normal user with no password using the spaces WebDAV API
When user "Alice" requests these endpoints with "MKCOL" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -137,7 +137,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send MKCOL requests to webDav endpoints without any authentication
When a user requests these endpoints with "MKCOL" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
@@ -148,7 +148,7 @@ Feature: create folder using MKCOL
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send MKCOL requests to webDav endpoints without any authentication using the spaces WebDAV API
When a user requests these endpoints with "MKCOL" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
tests/acceptance/features/coreApiAuthWebDav/webDavMOVEAuth.feature
+6 -6
View File
@@ -14,7 +14,7 @@ Feature: MOVE file/folder
And user "Alice" has created folder "/FOLDER"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send MOVE requests to webDav endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "MOVE" using password "invalid" about user "Alice"
| endpoint |
@@ -25,7 +25,7 @@ Feature: MOVE file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send MOVE requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
When user "Alice" requests these endpoints with "MOVE" using password "invalid" about user "Alice"
| endpoint |
@@ -34,7 +34,7 @@ Feature: MOVE file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send MOVE requests to webDav endpoints as normal user with no password
When user "Alice" requests these endpoints with "MOVE" using password "" about user "Alice"
| endpoint |
@@ -45,7 +45,7 @@ Feature: MOVE file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send MOVE requests to webDav endpoints as normal user with no password using the spaces WebDAV API
When user "Alice" requests these endpoints with "MOVE" using password "" about user "Alice"
| endpoint |
@@ -112,7 +112,7 @@ Feature: MOVE file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send MOVE requests to webDav endpoints without any authentication
When a user requests these endpoints with "MOVE" with no authentication about user "Alice"
| endpoint |
@@ -123,7 +123,7 @@ Feature: MOVE file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send MOVE requests to webDav endpoints without any authentication using the spaces WebDAV API
When a user requests these endpoints with "MOVE" with no authentication about user "Alice"
| endpoint |
tests/acceptance/features/coreApiAuthWebDav/webDavPOSTAuth.feature
+6 -6
View File
@@ -15,7 +15,7 @@ Feature: POST file/folder
And user "Alice" has created folder "/FOLDER"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send POST requests to webDav 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 |
@@ -26,7 +26,7 @@ Feature: POST file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send POST requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
@@ -35,7 +35,7 @@ Feature: POST file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send POST requests to webDav endpoints as normal user with no password
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -46,7 +46,7 @@ Feature: POST file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send POST requests to webDav endpoints as normal user with no password using the spaces WebDAV API
When user "Alice" requests these endpoints with "POST" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -113,7 +113,7 @@ Feature: POST file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send POST requests to webDav endpoints without any authentication
When a user requests these endpoints with "POST" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
@@ -124,7 +124,7 @@ Feature: POST file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send POST requests to webDav endpoints without any authentication using the spaces WebDAV API
When a user requests these endpoints with "POST" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
tests/acceptance/features/coreApiAuthWebDav/webDavPROPFINDAuth.feature
+6 -6
View File
@@ -14,7 +14,7 @@ Feature: PROPFIND file/folder
And user "Alice" has created folder "/FOLDER"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send PROPFIND requests to webDav endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "PROPFIND" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
@@ -25,7 +25,7 @@ Feature: PROPFIND file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send PROPFIND requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
When user "Alice" requests these endpoints with "PROPFIND" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
@@ -34,7 +34,7 @@ Feature: PROPFIND file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send PROPFIND requests to webDav endpoints as normal user with no password
When user "Alice" requests these endpoints with "PROPFIND" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -45,7 +45,7 @@ Feature: PROPFIND file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send PROPFIND requests to webDav endpoints as normal user with no password using the spaces WebDAV API
When user "Alice" requests these endpoints with "PROPFIND" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -112,7 +112,7 @@ Feature: PROPFIND file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send PROPFIND requests to webDav endpoints without any authentication
When a user requests these endpoints with "PROPFIND" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
@@ -123,7 +123,7 @@ Feature: PROPFIND file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send PROPFIND requests to webDav endpoints without any authentication using the spaces WebDAV API
When a user requests these endpoints with "PROPFIND" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
tests/acceptance/features/coreApiAuthWebDav/webDavPROPPATCHAuth.feature
+6 -6
View File
@@ -15,7 +15,7 @@ Feature: PROPPATCH file/folder
And user "Alice" has created folder "/FOLDER"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send PROPPATCH requests to webDav endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "PROPPATCH" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
@@ -26,7 +26,7 @@ Feature: PROPPATCH file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send PROPPATCH requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
When user "Alice" requests these endpoints with "PROPPATCH" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
@@ -35,7 +35,7 @@ Feature: PROPPATCH file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send PROPPATCH requests to webDav endpoints as normal user with no password
When user "Alice" requests these endpoints with "PROPPATCH" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -46,7 +46,7 @@ Feature: PROPPATCH file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send PROPPATCH requests to webDav endpoints as normal user with no password using the spaces WebDAV API
When user "Alice" requests these endpoints with "PROPPATCH" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -113,7 +113,7 @@ Feature: PROPPATCH file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send PROPPATCH requests to webDav endpoints without any authentication
When a user requests these endpoints with "PROPPATCH" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
@@ -124,7 +124,7 @@ Feature: PROPPATCH file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send PROPPATCH requests to webDav endpoints without any authentication using the spaces WebDAV API
When a user requests these endpoints with "PROPPATCH" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
tests/acceptance/features/coreApiAuthWebDav/webDavPUTAuth.feature
+6 -6
View File
@@ -15,7 +15,7 @@ Feature: PUT file/folder
And user "Alice" has created folder "/FOLDER"
And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send PUT requests to webDav endpoints as normal user with wrong password
When user "Alice" requests these endpoints with "PUT" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
@@ -26,7 +26,7 @@ Feature: PUT file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send PUT requests to webDav endpoints as normal user with wrong password using the spaces WebDAV API
When user "Alice" requests these endpoints with "PUT" including body "doesnotmatter" using password "invalid" about user "Alice"
| endpoint |
@@ -35,7 +35,7 @@ Feature: PUT file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send PUT requests to webDav endpoints as normal user with no password
When user "Alice" requests these endpoints with "PUT" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -46,7 +46,7 @@ Feature: PUT file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send PUT requests to webDav endpoints as normal user with no password using the spaces WebDAV API
When user "Alice" requests these endpoints with "PUT" including body "doesnotmatter" using password "" about user "Alice"
| endpoint |
@@ -119,7 +119,7 @@ Feature: PUT file/folder
| /remote.php/dav/spaces/%spaceid%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112
@smokeTest
Scenario: send PUT requests to webDav endpoints without any authentication
When a user requests these endpoints with "PUT" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |
@@ -130,7 +130,7 @@ Feature: PUT file/folder
| /remote.php/dav/files/%username%/PARENT/parent.txt |
Then the HTTP status code of responses on all endpoints should be "401"
@smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 @personalSpace
@smokeTest @personalSpace
Scenario: send PUT requests to webDav endpoints without any authentication using the spaces WebDAV API
When a user requests these endpoints with "PUT" with body "doesnotmatter" and no authentication about user "Alice"
| endpoint |