diff --git a/tests/acceptance/features/coreApiAuthOcs/ocsDELETEAuth.feature b/tests/acceptance/features/coreApiAuthOcs/ocsDELETEAuth.feature index 364fb27e8d..6dee5a4c2b 100644 --- a/tests/acceptance/features/coreApiAuthOcs/ocsDELETEAuth.feature +++ b/tests/acceptance/features/coreApiAuthOcs/ocsDELETEAuth.feature @@ -7,7 +7,7 @@ Feature: auth Background: Given user "another-admin" has been created with default attributes and without skeleton files - @smokeTest @issue-1337 @issue-1319 @skipOnBruteForceProtection @issue-brute_force_protection-112 + @smokeTest @issue-1337 @issue-1319 Scenario: send DELETE requests to OCS endpoints as admin with wrong password Given user "another-admin" has been added to group "admin" When user "another-admin" requests these endpoints with "DELETE" using password "invalid" about user "Alice" diff --git a/tests/acceptance/features/coreApiAuthOcs/ocsGETAuth.feature b/tests/acceptance/features/coreApiAuthOcs/ocsGETAuth.feature index 791900667d..3d9d08444c 100644 --- a/tests/acceptance/features/coreApiAuthOcs/ocsGETAuth.feature +++ b/tests/acceptance/features/coreApiAuthOcs/ocsGETAuth.feature @@ -72,7 +72,7 @@ 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 "401" - @issue-1338 @issue-1337 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 + @issue-1338 @issue-1337 @smokeTest Scenario: using OCS as normal user with wrong password When user "Alice" requests these endpoints with "GET" using password "invalid" | endpoint | @@ -120,7 +120,7 @@ Feature: auth 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" - @issue-1337 @issue-1319 @skipOnBruteForceProtection @issue-brute_force_protection-112 + @issue-1337 @issue-1319 Scenario: using OCS as admin user with wrong password Given user "another-admin" has been created with default attributes and without skeleton files And user "another-admin" has been added to group "admin" diff --git a/tests/acceptance/features/coreApiAuthOcs/ocsPOSTAuth.feature b/tests/acceptance/features/coreApiAuthOcs/ocsPOSTAuth.feature index c7c8e46fbd..d18ea766f8 100644 --- a/tests/acceptance/features/coreApiAuthOcs/ocsPOSTAuth.feature +++ b/tests/acceptance/features/coreApiAuthOcs/ocsPOSTAuth.feature @@ -7,7 +7,7 @@ Feature: auth Background: Given user "Alice" has been created with default attributes and without skeleton files - @issue-1337 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 + @issue-1337 @smokeTest 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 | diff --git a/tests/acceptance/features/coreApiAuthOcs/ocsPUTAuth.feature b/tests/acceptance/features/coreApiAuthOcs/ocsPUTAuth.feature index e979b30d5e..4ca72511f3 100644 --- a/tests/acceptance/features/coreApiAuthOcs/ocsPUTAuth.feature +++ b/tests/acceptance/features/coreApiAuthOcs/ocsPUTAuth.feature @@ -7,7 +7,7 @@ Feature: auth Background: Given user "another-admin" has been created with default attributes and without skeleton files - @issue-1337 @smokeTest @skipOnBruteForceProtection @issue-brute_force_protection-112 + @issue-1337 @smokeTest Scenario: send PUT request to OCS endpoints as admin with wrong password Given user "another-admin" has been added to group "admin" When user "another-admin" requests these endpoints with "PUT" including body "doesnotmatter" using password "invalid" about user "Alice" diff --git a/tests/acceptance/features/coreApiAuthWebDav/webDavCOPYAuth.feature b/tests/acceptance/features/coreApiAuthWebDav/webDavCOPYAuth.feature index 9ab6e65a2f..15910766d3 100644 --- a/tests/acceptance/features/coreApiAuthWebDav/webDavCOPYAuth.feature +++ b/tests/acceptance/features/coreApiAuthWebDav/webDavCOPYAuth.feature @@ -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 | diff --git a/tests/acceptance/features/coreApiAuthWebDav/webDavDELETEAuth.feature b/tests/acceptance/features/coreApiAuthWebDav/webDavDELETEAuth.feature index 6e2d17283b..f1a9ded106 100644 --- a/tests/acceptance/features/coreApiAuthWebDav/webDavDELETEAuth.feature +++ b/tests/acceptance/features/coreApiAuthWebDav/webDavDELETEAuth.feature @@ -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 | diff --git a/tests/acceptance/features/coreApiAuthWebDav/webDavLOCKAuth.feature b/tests/acceptance/features/coreApiAuthWebDav/webDavLOCKAuth.feature index cb6d4ecf18..08f7cf40df 100644 --- a/tests/acceptance/features/coreApiAuthWebDav/webDavLOCKAuth.feature +++ b/tests/acceptance/features/coreApiAuthWebDav/webDavLOCKAuth.feature @@ -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 | diff --git a/tests/acceptance/features/coreApiAuthWebDav/webDavMKCOLAuth.feature b/tests/acceptance/features/coreApiAuthWebDav/webDavMKCOLAuth.feature index 6b601f525b..6e74cbd94d 100644 --- a/tests/acceptance/features/coreApiAuthWebDav/webDavMKCOLAuth.feature +++ b/tests/acceptance/features/coreApiAuthWebDav/webDavMKCOLAuth.feature @@ -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 | diff --git a/tests/acceptance/features/coreApiAuthWebDav/webDavMOVEAuth.feature b/tests/acceptance/features/coreApiAuthWebDav/webDavMOVEAuth.feature index e8cadc1086..78ed5eb666 100644 --- a/tests/acceptance/features/coreApiAuthWebDav/webDavMOVEAuth.feature +++ b/tests/acceptance/features/coreApiAuthWebDav/webDavMOVEAuth.feature @@ -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 | diff --git a/tests/acceptance/features/coreApiAuthWebDav/webDavPOSTAuth.feature b/tests/acceptance/features/coreApiAuthWebDav/webDavPOSTAuth.feature index a2becf216b..425d035964 100644 --- a/tests/acceptance/features/coreApiAuthWebDav/webDavPOSTAuth.feature +++ b/tests/acceptance/features/coreApiAuthWebDav/webDavPOSTAuth.feature @@ -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 | diff --git a/tests/acceptance/features/coreApiAuthWebDav/webDavPROPFINDAuth.feature b/tests/acceptance/features/coreApiAuthWebDav/webDavPROPFINDAuth.feature index a352a7d99e..307d310df1 100644 --- a/tests/acceptance/features/coreApiAuthWebDav/webDavPROPFINDAuth.feature +++ b/tests/acceptance/features/coreApiAuthWebDav/webDavPROPFINDAuth.feature @@ -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 | diff --git a/tests/acceptance/features/coreApiAuthWebDav/webDavPROPPATCHAuth.feature b/tests/acceptance/features/coreApiAuthWebDav/webDavPROPPATCHAuth.feature index c19d3c6bdf..b7e59c7998 100644 --- a/tests/acceptance/features/coreApiAuthWebDav/webDavPROPPATCHAuth.feature +++ b/tests/acceptance/features/coreApiAuthWebDav/webDavPROPPATCHAuth.feature @@ -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 | diff --git a/tests/acceptance/features/coreApiAuthWebDav/webDavPUTAuth.feature b/tests/acceptance/features/coreApiAuthWebDav/webDavPUTAuth.feature index 18f84cfa7a..c45adc3005 100644 --- a/tests/acceptance/features/coreApiAuthWebDav/webDavPUTAuth.feature +++ b/tests/acceptance/features/coreApiAuthWebDav/webDavPUTAuth.feature @@ -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 |