[full-ci] ApiTests. enable auto accepting in api tests (#7477)

* enable auto accepting in test

* go format

.drone.env

@@ -1,3 +1,3 @@
 # The test runner source for UI tests
-WEB_COMMITID=a5b442ff9db3e9317cf163c6e2158e073ceb909d
+WEB_COMMITID=6fd967a12cfbe8fda936680ecf353c12eab78452
 WEB_BRANCH=master

.drone.star

@@ -48,6 +48,7 @@ dirs = {
     "ocis": "/srv/app/tmp/ocis",
     "ocisRevaDataRoot": "/srv/app/tmp/ocis/owncloud/data",
     "ocisWrapper": "/drone/src/tests/ociswrapper",
+    "bannedPasswordList": "tests/config/drone/banned-password-list.txt",
 }
 
 # configuration
@@ -1147,6 +1148,10 @@ def e2eTests(ctx):
         },
     }
 
+    extra_server_environment = {
+        "FRONTEND_PASSWORD_POLICY_BANNED_PASSWORDS_LIST": "%s" % dirs["bannedPasswordList"],
+    }
+
     e2e_trigger = {
         "ref": [
             "refs/heads/master",
@@ -1178,18 +1183,16 @@ def e2eTests(ctx):
             restoreWebCache() + \
             restoreWebPnpmCache() + \
             (tikaService() if suite["tikaNeeded"] else []) + \
-            ocisServer("ocis", 4, [], tika_enabled = suite["tikaNeeded"]) + \
+            ocisServer("ocis", 4, [], extra_server_environment = extra_server_environment, tika_enabled = suite["tikaNeeded"]) + \
             [{
                 "name": "e2e-tests",
                 "image": OC_CI_NODEJS % DEFAULT_NODEJS_VERSION,
                 "environment": {
                     "BASE_URL_OCIS": "ocis-server:9200",
                     "HEADLESS": "true",
-                    "OCIS": "true",
                     "RETRY": "1",
                     "WEB_UI_CONFIG_FILE": "%s/%s" % (dirs["base"], dirs["ocisConfig"]),
                     "LOCAL_UPLOAD_DIR": "/uploads",
-                    "API_TOKEN": "true",
                 },
                 "commands": [
                     "cd %s" % dirs["web"],

services/frontend/pkg/config/defaults/defaultconfig.go

@@ -120,6 +120,7 @@ func DefaultConfig() *config.Config {
 			},
 		},
 		LDAPServerWriteEnabled: true,
+		AutoAcceptShares:       true,
 		Events: config.Events{
 			Endpoint:  "127.0.0.1:9233",
 			Cluster:   "ocis-cluster",

tests/acceptance/config/behat-core.yml

@@ -75,6 +75,7 @@ default:
         - FeatureContext: *common_feature_context_params
         - TrashbinContext:
         - WebDavPropertiesContext:
+        - SettingsContext:
 
     coreApiShareCreateSpecialToShares2:
       paths:
@@ -84,6 +85,7 @@ default:
         - FeatureContext: *common_feature_context_params
         - TrashbinContext:
         - WebDavPropertiesContext:
+        - SettingsContext:
 
     coreApiSharees:
       paths:
@@ -103,6 +105,7 @@ default:
         - TrashbinContext:
         - WebDavPropertiesContext:
         - FilesVersionsContext:
+        - SettingsContext:
 
     coreApiShareManagementBasicToShares:
       paths:
@@ -124,6 +127,7 @@ default:
         - PublicWebDavContext:
         - TrashbinContext:
         - WebDavPropertiesContext:
+        - SettingsContext:
 
     coreApiShareOperationsToShares2:
       paths:

tests/acceptance/expected-failures-API-on-OCIS-storage.md

@@ -8,8 +8,8 @@ Basic file management like up and download, move, copy, properties, trash, versi
 
 #### [copy personal space file to shared folder root result share in decline state](https://github.com/owncloud/ocis/issues/6999)
 
-- [coreApiWebdavProperties1/copyFile.feature:289](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L289)
-- [coreApiWebdavProperties1/copyFile.feature:290](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L290)
+- [coreApiWebdavProperties1/copyFile.feature:285](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L285)
+- [coreApiWebdavProperties1/copyFile.feature:286](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L286)
 
 #### [Custom dav properties with namespaces are rendered incorrectly](https://github.com/owncloud/ocis/issues/2140)
 
@@ -34,16 +34,16 @@ _ocdav: double-check the webdav property parsing when custom namespaces are used
 #### [file versions do not report the version author](https://github.com/owncloud/ocis/issues/2914)
 
 - [coreApiVersions/fileVersionAuthor.feature:15](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L15)
-- [coreApiVersions/fileVersionAuthor.feature:46](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L46)
-- [coreApiVersions/fileVersionAuthor.feature:73](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L73)
-- [coreApiVersions/fileVersionAuthor.feature:99](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L99)
-- [coreApiVersions/fileVersionAuthor.feature:132](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L132)
-- [coreApiVersions/fileVersionAuthor.feature:159](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L159)
-- [coreApiVersions/fileVersionAuthor.feature:190](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L190)
-- [coreApiVersions/fileVersionAuthor.feature:225](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L225)
-- [coreApiVersions/fileVersionAuthor.feature:277](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L277)
-- [coreApiVersions/fileVersionAuthor.feature:326](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L326)
-- [coreApiVersions/fileVersionAuthor.feature:347](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L347)
+- [coreApiVersions/fileVersionAuthor.feature:43](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L43)
+- [coreApiVersions/fileVersionAuthor.feature:68](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L68)
+- [coreApiVersions/fileVersionAuthor.feature:92](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L92)
+- [coreApiVersions/fileVersionAuthor.feature:123](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L123)
+- [coreApiVersions/fileVersionAuthor.feature:148](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L148)
+- [coreApiVersions/fileVersionAuthor.feature:177](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L177)
+- [coreApiVersions/fileVersionAuthor.feature:208](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L208)
+- [coreApiVersions/fileVersionAuthor.feature:254](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L254)
+- [coreApiVersions/fileVersionAuthor.feature:297](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L297)
+- [coreApiVersions/fileVersionAuthor.feature:316](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature#L316)
 
 ### Sync
 
@@ -51,8 +51,8 @@ Synchronization features like etag propagation, setting mtime and locking files
 
 #### [Uploading an old method chunked file with checksum should fail using new DAV path](https://github.com/owncloud/ocis/issues/2323)
 
-- [coreApiMain/checksums.feature:260](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiMain/checksums.feature#L260)
-- [coreApiMain/checksums.feature:265](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiMain/checksums.feature#L265)
+- [coreApiMain/checksums.feature:258](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiMain/checksums.feature#L258)
+- [coreApiMain/checksums.feature:263](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiMain/checksums.feature#L263)
 
 #### [Webdav LOCK operations](https://github.com/owncloud/ocis/issues/1284)
 
@@ -74,9 +74,9 @@ Synchronization features like etag propagation, setting mtime and locking files
 - [coreApiWebdavLocks/exclusiveLocks.feature:106](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L106)
 - [coreApiWebdavLocks/exclusiveLocks.feature:111](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L111)
 - [coreApiWebdavLocks/exclusiveLocks.feature:112](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/exclusiveLocks.feature#L112)
+- [coreApiWebdavLocks/requestsWithToken.feature:31](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature#L31)
 - [coreApiWebdavLocks/requestsWithToken.feature:32](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature#L32)
-- [coreApiWebdavLocks/requestsWithToken.feature:33](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature#L33)
-- [coreApiWebdavLocks/requestsWithToken.feature:38](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature#L38)
+- [coreApiWebdavLocks/requestsWithToken.feature:37](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature#L37)
 - [coreApiWebdavLocks2/independentLocks.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L25)
 - [coreApiWebdavLocks2/independentLocks.feature:26](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L26)
 - [coreApiWebdavLocks2/independentLocks.feature:27](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L27)
@@ -95,18 +95,18 @@ Synchronization features like etag propagation, setting mtime and locking files
 - [coreApiWebdavLocks2/independentLocks.feature:66](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L66)
 - [coreApiWebdavLocks2/independentLocks.feature:67](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L67)
 - [coreApiWebdavLocks2/independentLocks.feature:68](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocks.feature#L68)
+- [coreApiWebdavLocks2/independentLocksShareToShares.feature:28](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L28)
+- [coreApiWebdavLocks2/independentLocksShareToShares.feature:29](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L29)
 - [coreApiWebdavLocks2/independentLocksShareToShares.feature:30](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L30)
 - [coreApiWebdavLocks2/independentLocksShareToShares.feature:31](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L31)
-- [coreApiWebdavLocks2/independentLocksShareToShares.feature:32](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L32)
-- [coreApiWebdavLocks2/independentLocksShareToShares.feature:33](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L33)
-- [coreApiWebdavLocks2/independentLocksShareToShares.feature:38](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L38)
-- [coreApiWebdavLocks2/independentLocksShareToShares.feature:39](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L39)
-- [coreApiWebdavLocks2/independentLocksShareToShares.feature:59](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L59)
-- [coreApiWebdavLocks2/independentLocksShareToShares.feature:60](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L60)
-- [coreApiWebdavLocks2/independentLocksShareToShares.feature:61](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L61)
-- [coreApiWebdavLocks2/independentLocksShareToShares.feature:62](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L62)
-- [coreApiWebdavLocks2/independentLocksShareToShares.feature:67](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L67)
-- [coreApiWebdavLocks2/independentLocksShareToShares.feature:68](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L68)
+- [coreApiWebdavLocks2/independentLocksShareToShares.feature:36](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L36)
+- [coreApiWebdavLocks2/independentLocksShareToShares.feature:37](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L37)
+- [coreApiWebdavLocks2/independentLocksShareToShares.feature:55](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L55)
+- [coreApiWebdavLocks2/independentLocksShareToShares.feature:56](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L56)
+- [coreApiWebdavLocks2/independentLocksShareToShares.feature:57](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L57)
+- [coreApiWebdavLocks2/independentLocksShareToShares.feature:58](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L58)
+- [coreApiWebdavLocks2/independentLocksShareToShares.feature:63](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L63)
+- [coreApiWebdavLocks2/independentLocksShareToShares.feature:64](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature#L64)
 - [coreApiWebdavLocksUnlock/unlock.feature:23](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L23)
 - [coreApiWebdavLocksUnlock/unlock.feature:24](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L24)
 - [coreApiWebdavLocksUnlock/unlock.feature:29](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L29)
@@ -118,36 +118,36 @@ Synchronization features like etag propagation, setting mtime and locking files
 - [coreApiWebdavLocksUnlock/unlock.feature:69](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L69)
 - [coreApiWebdavLocksUnlock/unlock.feature:74](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L74)
 - [coreApiWebdavLocksUnlock/unlock.feature:75](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlock.feature#L75)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:27](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L27)
 - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:28](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L28)
 - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:29](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L29)
 - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:30](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L30)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:31](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L31)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:35](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L35)
 - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:36](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L36)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:37](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L37)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:50](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L50)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:51](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L51)
 - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:52](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L52)
 - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:53](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L53)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:54](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L54)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:55](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L55)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:60](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L60)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:61](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L61)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:58](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L58)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:59](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L59)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:73](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L73)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:74](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L74)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:75](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L75)
 - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:76](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L76)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:77](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L77)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:78](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L78)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:79](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L79)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:84](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L84)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:85](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L85)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:100](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L100)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:101](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L101)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:102](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L102)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:103](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L103)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:108](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L108)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:109](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L109)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:124](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L124)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:125](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L125)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:126](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L126)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:81](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L81)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:82](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L82)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:96](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L96)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:97](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L97)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:98](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L98)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:99](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L99)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:104](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L104)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:105](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L105)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:119](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L119)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:120](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L120)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:121](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L121)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:122](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L122)
 - [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:127](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L127)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:132](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L132)
-- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:133](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L133)
+- [coreApiWebdavLocksUnlock/unlockSharingToShares.feature:128](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature#L128)
 
 ### Share
 
@@ -155,52 +155,51 @@ File and sync features in a shared scenario
 
 #### [accepting matching name shared resources from different users/groups sets no serial identifiers on the resource name for the receiver](https://github.com/owncloud/ocis/issues/4289)
 
-- [coreApiShareManagementToShares/acceptShares.feature:238](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L238)
-- [coreApiShareManagementToShares/acceptShares.feature:260](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L260)
-- [coreApiShareManagementToShares/acceptShares.feature:208](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L208)
-- [coreApiShareManagementToShares/acceptShares.feature:459](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L459)
-- [coreApiShareManagementToShares/acceptShares.feature:524](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L524)
+- [coreApiShareManagementToShares/acceptShares.feature:249](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L249)
+- [coreApiShareManagementToShares/acceptShares.feature:269](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L269)
+- [coreApiShareManagementToShares/acceptShares.feature:480](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L480)
+- [coreApiShareManagementToShares/acceptShares.feature:546](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L546)
 - [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:38](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L38)
 - [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:39](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L39)
-- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:127](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L127)
-- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:128](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L128)
-- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:160](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L160)
-- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:161](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L161)
+- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:125](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L125)
+- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:126](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L126)
+- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:158](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L158)
+- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:159](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L159)
 
 #### [sharing the shares folder to users exits with different status code than in oc10 backend](https://github.com/owncloud/ocis/issues/2215)
 
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:732](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L732)
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:733](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L733)
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:751](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L751)
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:752](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L752)
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:767](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L767)
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:768](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L768)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:648](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L648)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:649](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L649)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:666](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L666)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:667](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L667)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:681](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L681)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:682](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L682)
 
 #### [file_target of an auto-renamed file is not correct directly after sharing](https://github.com/owncloud/core/issues/32322)
 
-- [coreApiShareManagementToShares/mergeShare.feature:111](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature#L111)
+- [coreApiShareManagementToShares/mergeShare.feature:112](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature#L112)
 
 #### [File deletion using dav gives unique string in filename in the trashbin](https://github.com/owncloud/product/issues/178)
 
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:61](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L61)
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:75](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L75)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:58](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L58)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:71](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L71)
 
 cannot share a folder with create permission
 
 #### [Resource with share permission create is readable for sharee](https://github.com/owncloud/ocis/issues/4524)
 
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:125](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L125)
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:138](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L138)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:118](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L118)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:130](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L130)
 
 #### [OCS error message for attempting to access share via share id as an unauthorized user is not informative](https://github.com/owncloud/ocis/issues/1233)
 
-- [coreApiShareOperationsToShares1/gettingShares.feature:151](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature#L151)
-- [coreApiShareOperationsToShares1/gettingShares.feature:152](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature#L152)
+- [coreApiShareOperationsToShares1/gettingShares.feature:143](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature#L143)
+- [coreApiShareOperationsToShares1/gettingShares.feature:144](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature#L144)
 
 #### [Listing shares via ocs API does not show path for parent folders](https://github.com/owncloud/ocis/issues/1231)
 
-- [coreApiShareOperationsToShares1/gettingShares.feature:188](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature#L188)
-- [coreApiShareOperationsToShares1/gettingShares.feature:189](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature#L189)
+- [coreApiShareOperationsToShares1/gettingShares.feature:177](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature#L177)
+- [coreApiShareOperationsToShares1/gettingShares.feature:178](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature#L178)
 
 #### [Public link enforce permissions](https://github.com/owncloud/ocis/issues/1269)
 
@@ -227,67 +226,62 @@ cannot share a folder with create permission
 
 #### [deleting a file inside a received shared folder is moved to the trash-bin of the sharer not the receiver](https://github.com/owncloud/ocis/issues/1124)
 
-- [coreApiTrashbin/trashbinSharingToShares.feature:29](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L29)
-- [coreApiTrashbin/trashbinSharingToShares.feature:46](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L46)
-- [coreApiTrashbin/trashbinSharingToShares.feature:51](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L51)
-- [coreApiTrashbin/trashbinSharingToShares.feature:73](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L73)
-- [coreApiTrashbin/trashbinSharingToShares.feature:78](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L78)
-- [coreApiTrashbin/trashbinSharingToShares.feature:100](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L100)
-- [coreApiTrashbin/trashbinSharingToShares.feature:105](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L105)
-- [coreApiTrashbin/trashbinSharingToShares.feature:128](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L128)
-- [coreApiTrashbin/trashbinSharingToShares.feature:133](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L133)
-- [coreApiTrashbin/trashbinSharingToShares.feature:156](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L156)
-- [coreApiTrashbin/trashbinSharingToShares.feature:161](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L161)
-- [coreApiTrashbin/trashbinSharingToShares.feature:184](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L184)
-- [coreApiTrashbin/trashbinSharingToShares.feature:189](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L189)
-- [coreApiTrashbin/trashbinSharingToShares.feature:212](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L212)
-- [coreApiTrashbin/trashbinSharingToShares.feature:236](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L236)
+- [coreApiTrashbin/trashbinSharingToShares.feature:28](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L28)
+- [coreApiTrashbin/trashbinSharingToShares.feature:44](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L44)
+- [coreApiTrashbin/trashbinSharingToShares.feature:49](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L49)
+- [coreApiTrashbin/trashbinSharingToShares.feature:69](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L69)
+- [coreApiTrashbin/trashbinSharingToShares.feature:74](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L74)
+- [coreApiTrashbin/trashbinSharingToShares.feature:120](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L120)
+- [coreApiTrashbin/trashbinSharingToShares.feature:125](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L125)
+- [coreApiTrashbin/trashbinSharingToShares.feature:173](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L173)
+- [coreApiTrashbin/trashbinSharingToShares.feature:178](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L178)
+- [coreApiTrashbin/trashbinSharingToShares.feature:200](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L200)
+- [coreApiTrashbin/trashbinSharingToShares.feature:223](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature#L223)
 
 #### [changing user quota gives ocs status 103 / Cannot set quota](https://github.com/owncloud/product/issues/247)
 
-- [coreApiShareOperationsToShares2/uploadToShare.feature:210](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/uploadToShare.feature#L210)
-- [coreApiShareOperationsToShares2/uploadToShare.feature:211](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/uploadToShare.feature#L211)
+- [coreApiShareOperationsToShares2/uploadToShare.feature:201](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/uploadToShare.feature#L201)
+- [coreApiShareOperationsToShares2/uploadToShare.feature:202](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/uploadToShare.feature#L202)
 
 #### [not possible to move file into a received folder](https://github.com/owncloud/ocis/issues/764)
 
+- [coreApiShareOperationsToShares1/changingFilesShare.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature#L25)
 - [coreApiShareOperationsToShares1/changingFilesShare.feature:26](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature#L26)
-- [coreApiShareOperationsToShares1/changingFilesShare.feature:27](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature#L27)
-- [coreApiShareOperationsToShares1/changingFilesShare.feature:70](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature#L70)
-- [coreApiShareOperationsToShares1/changingFilesShare.feature:71](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature#L71)
-- [coreApiShareOperationsToShares1/changingFilesShare.feature:92](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature#L92)
-- [coreApiShareOperationsToShares1/changingFilesShare.feature:93](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature#L93)
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:532](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L532)
-- [coreApiWebdavMove2/moveShareOnOcis.feature:29](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L29)
-- [coreApiWebdavMove2/moveShareOnOcis.feature:31](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L31)
-- [coreApiWebdavMove2/moveShareOnOcis.feature:97](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L97)
-- [coreApiWebdavMove2/moveShareOnOcis.feature:99](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L99)
-- [coreApiWebdavMove2/moveShareOnOcis.feature:168](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L168)
-- [coreApiWebdavMove2/moveShareOnOcis.feature:169](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L169)
+- [coreApiShareOperationsToShares1/changingFilesShare.feature:65](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature#L65)
+- [coreApiShareOperationsToShares1/changingFilesShare.feature:66](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature#L66)
+- [coreApiShareOperationsToShares1/changingFilesShare.feature:85](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature#L85)
+- [coreApiShareOperationsToShares1/changingFilesShare.feature:86](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature#L86)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:468](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L468)
+- [coreApiWebdavMove2/moveShareOnOcis.feature:28](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L28)
+- [coreApiWebdavMove2/moveShareOnOcis.feature:30](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L30)
+- [coreApiWebdavMove2/moveShareOnOcis.feature:93](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L93)
+- [coreApiWebdavMove2/moveShareOnOcis.feature:95](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L95)
+- [coreApiWebdavMove2/moveShareOnOcis.feature:161](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L161)
+- [coreApiWebdavMove2/moveShareOnOcis.feature:162](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature#L162)
 
 #### [Expiration date for shares is not implemented](https://github.com/owncloud/ocis/issues/1250)
 
 #### Expiration date of user shares
 
-- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:35](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L35)
-- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:36](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L36)
+- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:33](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L33)
+- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:34](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L34)
 
 #### Expiration date of group shares
 
-- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:60](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L60)
-- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:61](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L61)
+- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:56](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L56)
+- [coreApiShareReshareToShares3/reShareWithExpiryDate.feature:57](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature#L57)
 
 #### [Cannot move folder/file from one received share to another](https://github.com/owncloud/ocis/issues/2442)
 
-- [coreApiShareUpdateToShares/updateShare.feature:160](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L160)
-- [coreApiShareUpdateToShares/updateShare.feature:128](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L128)
-- [coreApiShareManagementToShares/mergeShare.feature:131](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature#L131)
+- [coreApiShareUpdateToShares/updateShare.feature:123](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L123)
+- [coreApiShareUpdateToShares/updateShare.feature:153](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L153)
 
 #### [Sharing folder and sub-folder with same user but different permission,the permission of sub-folder is not obeyed ](https://github.com/owncloud/ocis/issues/2440)
 
-- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:220](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L220)
-- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:350](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L350)
-- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:251](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L251)
-- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:381](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L381)
+- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:212](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L212)
+- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:323](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L323)
+- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:349](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L349)
+- [coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature:238](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature#L238)
 
 #### [Empty OCS response for a share create request using a disabled user](https://github.com/owncloud/ocis/issues/2212)
 
@@ -296,18 +290,18 @@ cannot share a folder with create permission
 
 #### [Edit user share response has a "name" field](https://github.com/owncloud/ocis/issues/1225)
 
-- [coreApiShareUpdateToShares/updateShare.feature:235](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L235)
-- [coreApiShareUpdateToShares/updateShare.feature:236](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L236)
+- [coreApiShareUpdateToShares/updateShare.feature:226](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L226)
+- [coreApiShareUpdateToShares/updateShare.feature:227](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature#L227)
 
 #### [Share lists deleted user as 'user'](https://github.com/owncloud/ocis/issues/903)
 
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:667](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L667)
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:668](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L668)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:588](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L588)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:589](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L589)
 
 #### [deleting a share with wrong authentication returns OCS status 996 / HTTP 500](https://github.com/owncloud/ocis/issues/1229)
 
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:221](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L221)
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:222](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L222)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:207](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L207)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:208](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L208)
 
 ### User Management
 
@@ -317,6 +311,7 @@ User and group management features
 
 _ocs: api compatibility, return correct status code_
 
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:47](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L47)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:48](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L48)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:49](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L49)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:50](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L50)
@@ -324,7 +319,6 @@ _ocs: api compatibility, return correct status code_
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:52](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L52)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:53](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L53)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:54](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L54)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:55](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L55)
 
 ### Other
 
@@ -422,8 +416,8 @@ And other missing implementation of favorites
 - [coreApiFavorites/favorites.feature:202](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiFavorites/favorites.feature#L202)
 - [coreApiFavorites/favorites.feature:203](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiFavorites/favorites.feature#L203)
 - [coreApiFavorites/favorites.feature:208](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiFavorites/favorites.feature#L208)
-- [coreApiFavorites/favoritesSharingToShares.feature:67](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiFavorites/favoritesSharingToShares.feature#L67)
-- [coreApiFavorites/favoritesSharingToShares.feature:68](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiFavorites/favoritesSharingToShares.feature#L68)
+- [coreApiFavorites/favoritesSharingToShares.feature:63](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiFavorites/favoritesSharingToShares.feature#L63)
+- [coreApiFavorites/favoritesSharingToShares.feature:64](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiFavorites/favoritesSharingToShares.feature#L64)
 
 #### [WWW-Authenticate header for unauthenticated requests is not clear](https://github.com/owncloud/ocis/issues/2285)
 
@@ -436,8 +430,8 @@ And other missing implementation of favorites
 
 #### [Sharing a same file twice to the same group](https://github.com/owncloud/ocis/issues/1710)
 
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:715](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L715)
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:716](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L716)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:632](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L632)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:633](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L633)
 
 #### [PATCH request for TUS upload with wrong checksum gives incorrect response](https://github.com/owncloud/ocis/issues/1755)
 
@@ -464,16 +458,16 @@ And other missing implementation of favorites
 - [coreApiWebdavUploadTUS/checksums.feature:293](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/checksums.feature#L293)
 - [coreApiWebdavUploadTUS/optionsRequest.feature:10](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature#L10)
 - [coreApiWebdavUploadTUS/optionsRequest.feature:25](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/optionsRequest.feature#L25)
-- [coreApiWebdavUploadTUS/uploadToShare.feature:175](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L175)
-- [coreApiWebdavUploadTUS/uploadToShare.feature:176](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L176)
-- [coreApiWebdavUploadTUS/uploadToShare.feature:194](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L194)
-- [coreApiWebdavUploadTUS/uploadToShare.feature:195](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L195)
-- [coreApiWebdavUploadTUS/uploadToShare.feature:213](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L213)
-- [coreApiWebdavUploadTUS/uploadToShare.feature:214](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L214)
-- [coreApiWebdavUploadTUS/uploadToShare.feature:252](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L252)
-- [coreApiWebdavUploadTUS/uploadToShare.feature:253](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L253)
-- [coreApiWebdavUploadTUS/uploadToShare.feature:294](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L294)
-- [coreApiWebdavUploadTUS/uploadToShare.feature:295](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L295)
+- [coreApiWebdavUploadTUS/uploadToShare.feature:165](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L165)
+- [coreApiWebdavUploadTUS/uploadToShare.feature:166](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L166)
+- [coreApiWebdavUploadTUS/uploadToShare.feature:183](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L183)
+- [coreApiWebdavUploadTUS/uploadToShare.feature:184](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L184)
+- [coreApiWebdavUploadTUS/uploadToShare.feature:201](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L201)
+- [coreApiWebdavUploadTUS/uploadToShare.feature:202](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L202)
+- [coreApiWebdavUploadTUS/uploadToShare.feature:238](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L238)
+- [coreApiWebdavUploadTUS/uploadToShare.feature:239](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L239)
+- [coreApiWebdavUploadTUS/uploadToShare.feature:278](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L278)
+- [coreApiWebdavUploadTUS/uploadToShare.feature:279](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature#L279)
 
 #### [TUS OPTIONS requests do not reply with TUS headers when invalid password](https://github.com/owncloud/ocis/issues/1012)
 
@@ -482,42 +476,42 @@ And other missing implementation of favorites
 
 #### [Trying to accept a share with invalid ID gives incorrect OCS and HTTP status](https://github.com/owncloud/ocis/issues/2111)
 
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:81](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L81)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:82](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L82)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:83](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L83)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:84](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L84)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:85](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L85)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:86](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L86)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:87](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L87)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:88](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L88)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:89](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L89)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:90](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L90)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:91](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L91)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:102](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L102)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:103](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L103)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:98](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L98)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:99](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L99)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:128](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L128)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:129](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L129)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:130](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L130)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:131](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L131)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:132](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L132)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:133](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L133)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:134](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L134)
 - [coreApiShareOperationsToShares2/shareAccessByID.feature:135](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L135)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:136](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L136)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:137](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L137)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:138](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L138)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:139](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L139)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:140](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L140)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:151](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L151)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:152](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L152)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:146](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L146)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:147](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L147)
 
 #### [Shares to deleted group listed in the response](https://github.com/owncloud/ocis/issues/2441)
 
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:528](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L528)
-- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:529](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L529)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:464](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L464)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:465](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L465)
 
 #### [copying the file inside Shares folder returns 404](https://github.com/owncloud/ocis/issues/3874)
 
-- [coreApiWebdavProperties1/copyFile.feature:407](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L407)
-- [coreApiWebdavProperties1/copyFile.feature:408](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L408)
-- [coreApiWebdavProperties1/copyFile.feature:413](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L413)
-- [coreApiWebdavProperties1/copyFile.feature:433](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L433)
-- [coreApiWebdavProperties1/copyFile.feature:434](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L434)
-- [coreApiWebdavProperties1/copyFile.feature:439](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L439)
-- [coreApiWebdavProperties1/copyFile.feature:271](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L271)
-- [coreApiWebdavProperties1/copyFile.feature:272](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L272)
+- [coreApiWebdavProperties1/copyFile.feature:398](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L398)
+- [coreApiWebdavProperties1/copyFile.feature:399](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L399)
+- [coreApiWebdavProperties1/copyFile.feature:404](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L404)
+- [coreApiWebdavProperties1/copyFile.feature:423](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L423)
+- [coreApiWebdavProperties1/copyFile.feature:424](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L424)
+- [coreApiWebdavProperties1/copyFile.feature:429](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L429)
+- [coreApiWebdavProperties1/copyFile.feature:268](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L268)
+- [coreApiWebdavProperties1/copyFile.feature:269](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L269)
 
 ### Won't fix
 
@@ -528,9 +522,9 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers
 
 #### [Blacklist files extensions](https://github.com/owncloud/ocis/issues/2177)
 
-- [coreApiWebdavProperties1/copyFile.feature:117](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L117)
-- [coreApiWebdavProperties1/copyFile.feature:118](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L118)
-- [coreApiWebdavProperties1/copyFile.feature:123](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L123)
+- [coreApiWebdavProperties1/copyFile.feature:115](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L115)
+- [coreApiWebdavProperties1/copyFile.feature:116](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L116)
+- [coreApiWebdavProperties1/copyFile.feature:121](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature#L121)
 - [coreApiWebdavProperties1/createFileFolder.feature:97](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/createFileFolder.feature#L97)
 - [coreApiWebdavProperties1/createFileFolder.feature:98](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/createFileFolder.feature#L98)
 - [coreApiWebdavProperties1/createFileFolder.feature:103](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavProperties1/createFileFolder.feature#L103)
@@ -552,22 +546,22 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers
 #### [Share path in the response is different between share states](https://github.com/owncloud/ocis/issues/2540)
 
 - [coreApiShareManagementToShares/acceptShares.feature:28](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L28)
-- [coreApiShareManagementToShares/acceptShares.feature:62](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L62)
-- [coreApiShareManagementToShares/acceptShares.feature:134](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L134)
-- [coreApiShareManagementToShares/acceptShares.feature:155](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L155)
-- [coreApiShareManagementToShares/acceptShares.feature:183](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L183)
-- [coreApiShareManagementToShares/acceptShares.feature:228](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L228)
-- [coreApiShareManagementToShares/acceptShares.feature:438](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L438)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:121](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L121)
-- [coreApiShareOperationsToShares2/shareAccessByID.feature:122](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L122)
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:172](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L172)
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:173](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L173)
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:174](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L174)
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:175](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L175)
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:191](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L191)
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:192](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L192)
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:193](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L193)
-- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:194](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L194)
+- [coreApiShareManagementToShares/acceptShares.feature:64](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L64)
+- [coreApiShareManagementToShares/acceptShares.feature:139](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L139)
+- [coreApiShareManagementToShares/acceptShares.feature:161](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L161)
+- [coreApiShareManagementToShares/acceptShares.feature:190](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L190)
+- [coreApiShareManagementToShares/acceptShares.feature:238](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L238)
+- [coreApiShareManagementToShares/acceptShares.feature:457](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L457)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:116](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L116)
+- [coreApiShareOperationsToShares2/shareAccessByID.feature:117](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature#L117)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:161](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L161)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:162](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L162)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:163](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L163)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:164](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L164)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:179](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L179)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:180](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L180)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:181](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L181)
+- [coreApiShareManagementBasicToShares/deleteShareFromShares.feature:182](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature#L182)
 
 #### [Content-type is not multipart/byteranges when downloading file with Range Header](https://github.com/owncloud/ocis/issues/2677)
 
@@ -577,9 +571,9 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers
 
 #### [moveShareInsideAnotherShare behaves differently on oCIS than oC10](https://github.com/owncloud/ocis/issues/3047)
 
-- [coreApiShareManagementToShares/moveShareInsideAnotherShare.feature:22](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/moveShareInsideAnotherShare.feature#L22)
-- [coreApiShareManagementToShares/moveShareInsideAnotherShare.feature:42](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/moveShareInsideAnotherShare.feature#L42)
-- [coreApiShareManagementToShares/moveShareInsideAnotherShare.feature:56](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/moveShareInsideAnotherShare.feature#L56)
+- [coreApiShareManagementToShares/moveShareInsideAnotherShare.feature:20](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/moveShareInsideAnotherShare.feature#L20)
+- [coreApiShareManagementToShares/moveShareInsideAnotherShare.feature:40](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/moveShareInsideAnotherShare.feature#L40)
+- [coreApiShareManagementToShares/moveShareInsideAnotherShare.feature:54](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/moveShareInsideAnotherShare.feature#L54)
 
 #### [Renaming resource to banned name is allowed in spaces webdav](https://github.com/owncloud/ocis/issues/3099)
 
@@ -611,8 +605,22 @@ Not everything needs to be implemented for ocis. While the oc10 testsuite covers
 
 #### [sharing the shares folder to users exits with different status code than in oc10 backend](https://github.com/owncloud/ocis/issues/2215)
 
+- [coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature:22](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature#L22)
 - [coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature:23](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature#L23)
-- [coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature:24](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature#L24)
+
+#### [List of failed tests after enabling auto-accept] (https://github.com/owncloud/ocis/issues/7504)
+- [coreApiWebdavPreviews/previews.feature:224](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiWebdavPreviews/previews.feature#L224)
+- [coreApiShareManagementToShares/acceptShares.feature:217](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature#L217)
+- [coreApiShareManagementToShares/mergeShare.feature:132](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature#L132)
+- [coreApiShareOperationsToShares1/gettingShares.feature:99](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature#L99)
+- [coreApiShareOperationsToShares1/gettingShares.feature:100](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature#L100)
+- [coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature:41](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature#L41)
+- [coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature:42](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature#L42)
+- [coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature:54](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature#L54)
+- [coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature:55](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature#L55)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:235](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L235)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:429](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L429)
+- [coreApiShareManagementBasicToShares/createShareToSharesFolder.feature:430](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature#L430)
 
 Note: always have an empty line at the end of this file.
 The bash script that processes this file requires that the last line has a newline on the end.

tests/acceptance/expected-failures-localAPI-on-OCIS-storage.md

@@ -10,13 +10,13 @@ The expected failures in this file are from features in the owncloud/ocis repo.
 - [apiArchiver/downloadByPath.feature:44](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiArchiver/downloadByPath.feature#L44)
 - [apiArchiver/downloadByPath.feature:47](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiArchiver/downloadByPath.feature#L47)
 - [apiArchiver/downloadByPath.feature:73](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiArchiver/downloadByPath.feature#L73)
-- [apiArchiver/downloadByPath.feature:131](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiArchiver/downloadByPath.feature#L131)
-- [apiArchiver/downloadByPath.feature:132](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiArchiver/downloadByPath.feature#L132)
+- [apiArchiver/downloadByPath.feature:123](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiArchiver/downloadByPath.feature#L123)
+- [apiArchiver/downloadByPath.feature:124](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiArchiver/downloadByPath.feature#L124)
 
 ### [Downloaded /Shares tar contains resource (files|folder) with leading / in Response](https://github.com/owncloud/ocis/issues/4636)
 
-- [apiArchiver/downloadById.feature:133](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiArchiver/downloadById.feature#L133)
-- [apiArchiver/downloadById.feature:134](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiArchiver/downloadById.feature#L134)
+- [apiArchiver/downloadById.feature:125](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiArchiver/downloadById.feature#L125)
+- [apiArchiver/downloadById.feature:126](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiArchiver/downloadById.feature#L126)
 
 ### [PROPFIND on accepted shares with identical names containing brackets exit with 404](https://github.com/owncloud/ocis/issues/4421)
 
@@ -24,14 +24,14 @@ The expected failures in this file are from features in the owncloud/ocis repo.
 
 ### [Shared mount folder gets deleted when overwritten by a file from personal space](https://github.com/owncloud/ocis/issues/7208)
 
-- [apiSpacesShares/copySpaces.feature:528](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiSpacesShares/copySpaces.feature#L528)
-- [apiSpacesShares/copySpaces.feature:542](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiSpacesShares/copySpaces.feature#L542)
+- [apiSpacesShares/copySpaces.feature:510](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiSpacesShares/copySpaces.feature#L510)
+- [apiSpacesShares/copySpaces.feature:523](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiSpacesShares/copySpaces.feature#L523)
 
 #### [PATCH request for TUS upload with wrong checksum gives incorrect response](https://github.com/owncloud/ocis/issues/1755)
 
-- [apiSpacesShares/shareUploadTUS.feature:203](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature#L203)
-- [apiSpacesShares/shareUploadTUS.feature:218](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature#L218)
-- [apiSpacesShares/shareUploadTUS.feature:283](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature#L283)
+- [apiSpacesShares/shareUploadTUS.feature:187](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature#L187)
+- [apiSpacesShares/shareUploadTUS.feature:201](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature#L201)
+- [apiSpacesShares/shareUploadTUS.feature:264](https://github.com/owncloud/ocis/blob/master/tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature#L264)
 
 ### [Settings service user can list other peoples assignments](https://github.com/owncloud/ocis/issues/5032)
 

tests/acceptance/expected-failures-webUI-on-OCIS-storage.md

@@ -29,27 +29,27 @@ Other free text and Markdown formatting can be used elsewhere in the document if
 -   [webUIFavorites/unfavoriteFile.feature:70](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUIFavorites/unfavoriteFile.feature#L70)
 -   [webUIFavorites/unfavoriteFile.feature:86](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUIFavorites/unfavoriteFile.feature#L87)
 -   [webUIFavorites/unfavoriteFile.feature:101](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUIFavorites/unfavoriteFile.feature#L102)
--   [webUIResharing1/reshareUsers.feature:177](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUIResharing1/reshareUsers.feature#L177)
+-   [webUIResharing1/reshareUsers.feature:68](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUIResharing1/reshareUsers.feature#L68)
 
 ### [when sharer renames the shared resource, sharee get the updated name](https://github.com/owncloud/ocis/issues/2256)
 -   [webUIRenameFiles/renameFiles.feature:227](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUIRenameFiles/renameFiles.feature#L227)
 
 ### [Cannot create users with special characters](https://github.com/owncloud/ocis/issues/1417)
+-   [webUISharingAutocompletion/shareAutocompletionSpecialChars.feature:35](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletionSpecialChars.feature#L35)
+-   [webUISharingAutocompletion/shareAutocompletionSpecialChars.feature:36](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletionSpecialChars.feature#L36)
 -   [webUISharingAutocompletion/shareAutocompletionSpecialChars.feature:37](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletionSpecialChars.feature#L37)
 -   [webUISharingAutocompletion/shareAutocompletionSpecialChars.feature:38](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletionSpecialChars.feature#L38)
--   [webUISharingAutocompletion/shareAutocompletionSpecialChars.feature:39](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletionSpecialChars.feature#L39)
--   [webUISharingAutocompletion/shareAutocompletionSpecialChars.feature:36](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingAutocompletion/shareAutocompletionSpecialChars.feature#L36)
 
 ### [Share additional info](https://github.com/owncloud/ocis/issues/1253)
--   [webUISharingInternalUsersShareWithPage/shareWithUsers.feature:138](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingInternalUsersShareWithPage/shareWithUsers.feature#L138)
+-   [webUISharingInternalUsersShareWithPage/shareWithUsers.feature:126](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingInternalUsersShareWithPage/shareWithUsers.feature#L126)
 
 ### [Expiration date set is not implemented in user share](https://github.com/owncloud/ocis/issues/1250)
--   [webUISharingInternalGroups/shareWithGroups.feature:244](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingInternalGroups/shareWithGroups.feature#L244)
+-   [webUISharingInternalGroups/shareWithGroups.feature:228](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingInternalGroups/shareWithGroups.feature#L228)
 
 ### [Different path for shares inside folder](https://github.com/owncloud/ocis/issues/1231)
 
 ### [Implement expiration date for shares](https://github.com/owncloud/ocis/issues/1250)
-- [webUISharingInternalGroups/shareWithGroups.feature:222](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingInternalGroups/shareWithGroups.feature#L222)
+- [webUISharingInternalGroups/shareWithGroups.feature:208](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingInternalGroups/shareWithGroups.feature#L208)
 - [webUISharingExpirationDate/shareWithExpirationDate.feature:21](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingExpirationDate/shareWithExpirationDate.feature#L21)
 
 ### [Notifications endpoint](https://github.com/owncloud/ocis/issues/14)
@@ -120,4 +120,4 @@ Other free text and Markdown formatting can be used elsewhere in the document if
 -   [webUIRenameFiles/renameFiles.feature:250](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUIRenameFiles/renameFiles.feature#L250)
 
 ### [PROPFIND to sub-folder of a shared resources with same name gives 404](https://github.com/owncloud/ocis/issues/3859)
--   [webUISharingAcceptShares/acceptShares.feature:240](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingAcceptShares/acceptShares.feature#L240)
+-   [webUISharingAcceptShares/acceptShares.feature:163](https://github.com/owncloud/web/blob/master/tests/acceptance/features/webUISharingAcceptShares/acceptShares.feature#L163)

tests/acceptance/features/apiAccountsHashDifficulty/createShareToSharesFolder.feature

@@ -14,10 +14,8 @@ Feature: sharing
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     And user "Brian" has been created with default attributes and without skeleton files
     When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API
-    And user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
-    Then the HTTP status code should be "200"
     And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
     Examples:
       | ocs_api_version |
       | 1               |
-      | 2               |
+      | 2               |

tests/acceptance/features/apiAntivirus/antivirus.feature

@@ -140,7 +140,6 @@ Feature: antivirus
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "uploadFolder"
     And user "Alice" has shared folder "uploadFolder" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/uploadFolder" offered by user "Alice"
     When user "Brian" uploads file "filesForUpload/filesWithVirus/<filename>" to "/Shares/uploadFolder/<newfilename>" using the WebDAV API
     Then the HTTP status code should be "201"
     And user "Brian" should get a notification with subject "Virus found" and message:
@@ -161,7 +160,6 @@ Feature: antivirus
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "uploadFolder"
     And user "Alice" has shared folder "uploadFolder" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/uploadFolder" offered by user "Alice"
     When user "Brian" uploads a file "filesForUpload/filesWithVirus/<filename>" to "/uploadFolder/<newfilename>" in space "Shares" using the WebDAV API
     Then the HTTP status code should be "201"
     And user "Brian" should get a notification with subject "Virus found" and message:
@@ -182,7 +180,6 @@ Feature: antivirus
     And user "Brian" has been added to group "group1"
     And user "Alice" has created folder "uploadFolder"
     And user "Alice" has shared folder "uploadFolder" with group "group1"
-    And user "Brian" has accepted share "/uploadFolder" offered by user "Alice"
     When user "Brian" uploads file "filesForUpload/filesWithVirus/<filename>" to "/Shares/uploadFolder/<newfilename>" using the WebDAV API
     Then the HTTP status code should be "201"
     And user "Brian" should get a notification with subject "Virus found" and message:
@@ -205,7 +202,6 @@ Feature: antivirus
     And user "Brian" has been added to group "group1"
     And user "Alice" has created folder "uploadFolder"
     And user "Alice" has shared folder "uploadFolder" with group "group1"
-    And user "Brian" has accepted share "/uploadFolder" offered by user "Alice"
     When user "Brian" uploads a file "filesForUpload/filesWithVirus/<filename>" to "/uploadFolder/<newfilename>" in space "Shares" using the WebDAV API
     Then the HTTP status code should be "201"
     And user "Brian" should get a notification with subject "Virus found" and message:
@@ -378,7 +374,6 @@ Feature: antivirus
     And user "Alice" has been added to group "group1"
     And user "Alice" has uploaded file with content "hello" to "/test.txt"
     And user "Alice" has shared file "test.txt" with group "group1"
-    And user "Brian" has accepted share "/test.txt" offered by user "Alice"
     When user "Brian" uploads file with content "X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*" to "test.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And user "Brian" should get a notification with subject "Virus found" and message:
@@ -400,7 +395,6 @@ Feature: antivirus
     And user "Alice" has been added to group "group1"
     And user "Alice" has uploaded file with content "hello" to "/test.txt"
     And user "Alice" has shared file "test.txt" with group "group1"
-    And user "Brian" has accepted share "/test.txt" offered by user "Alice"
     When user "Brian" uploads a file "filesForUpload/filesWithVirus/eicar.com" to "/test.txt" in space "Shares" using the WebDAV API
     Then the HTTP status code should be "204"
     And user "Brian" should get a notification with subject "Virus found" and message:
@@ -418,8 +412,6 @@ Feature: antivirus
     And user "Alice" has shared folder "uploadFolder" with user "Brian" with permissions "all"
     And user "Alice" has uploaded file with content "this is a test file." to "/test.txt"
     And user "Alice" has shared file "/test.txt" with user "Brian"
-    And user "Brian" has accepted share "/uploadFolder" offered by user "Alice"
-    And user "Brian" has accepted share "/test.txt" offered by user "Alice"
     When user "Brian" uploads file with content "X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*" to "Shares/uploadFolder/test.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And user "Brian" should get a notification for resource "test.txt" with subject "Virus found" and message:
@@ -448,8 +440,6 @@ Feature: antivirus
     And user "Alice" has shared folder "uploadFolder" with user "Brian" with permissions "all"
     And user "Alice" has uploaded file with content "this is a test file." to "/test.txt"
     And user "Alice" has shared file "/test.txt" with user "Brian"
-    And user "Brian" has accepted share "/uploadFolder" offered by user "Alice"
-    And user "Brian" has accepted share "/test.txt" offered by user "Alice"
     When user "Brian" uploads a file "filesForUpload/filesWithVirus/eicar.com" to "/uploadFolder/test.txt" in space "Shares" using the WebDAV API
     Then the HTTP status code should be "204"
     And user "Brian" should get a notification for resource "test.txt" with subject "Virus found" and message:

tests/acceptance/features/apiArchiver/downloadById.feature

@@ -84,10 +84,6 @@ Feature: download multiple resources bundled into an archive
     And user "Alice" has shared file "textfile1.txt" with user "Brian"
     And user "Alice" has shared folder "my_data" with user "Brian"
     And user "Alice" has shared folder "more_data" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
-    And user "Brian" has accepted share "/textfile1.txt" offered by user "Alice"
-    And user "Brian" has accepted share "/my_data" offered by user "Alice"
-    And user "Brian" has accepted share "/more_data" offered by user "Alice"
     When user "Brian" downloads the archive of these items using the resource ids
       | /Shares/textfile0.txt |
       | /Shares/textfile1.txt |
@@ -114,10 +110,6 @@ Feature: download multiple resources bundled into an archive
     And user "Alice" has shared file "textfile1.txt" with user "Brian"
     And user "Alice" has shared folder "my_data" with user "Brian"
     And user "Alice" has shared folder "more_data" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
-    And user "Brian" has accepted share "/textfile1.txt" offered by user "Alice"
-    And user "Brian" has accepted share "/my_data" offered by user "Alice"
-    And user "Brian" has accepted share "/more_data" offered by user "Alice"
     When user "Brian" downloads the archive of "/Shares" using the resource id and setting these headers
       | header     | value        |
       | User-Agent | <user-agent> |

tests/acceptance/features/apiArchiver/downloadByPath.feature

@@ -82,10 +82,6 @@ Feature: download multiple resources bundled into an archive
     And user "Alice" has shared file "textfile1.txt" with user "Brian"
     And user "Alice" has shared folder "my_data" with user "Brian"
     And user "Alice" has shared folder "more_data" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
-    And user "Brian" has accepted share "/textfile1.txt" offered by user "Alice"
-    And user "Brian" has accepted share "/my_data" offered by user "Alice"
-    And user "Brian" has accepted share "/more_data" offered by user "Alice"
     When user "Brian" downloads the archive of these items using the resource path
       | /home/Shares/textfile0.txt |
       | /home/Shares/textfile1.txt |
@@ -112,10 +108,6 @@ Feature: download multiple resources bundled into an archive
     And user "Alice" has shared file "textfile1.txt" with user "Brian"
     And user "Alice" has shared folder "my_data" with user "Brian"
     And user "Alice" has shared folder "more_data" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
-    And user "Brian" has accepted share "/textfile1.txt" offered by user "Alice"
-    And user "Brian" has accepted share "/my_data" offered by user "Alice"
-    And user "Brian" has accepted share "/more_data" offered by user "Alice"
     When user "Brian" downloads the archive of "/home/Shares" using the resource path and setting these headers
       | header     | value        |
       | User-Agent | <user-agent> |

tests/acceptance/features/apiContract/sharesReport.feature

@@ -16,7 +16,6 @@ Feature: REPORT request to Shares space
 
   Scenario Outline: check the REPORT response of the found folder
     Given using <dav-path-version> DAV path
-    And user "Brian" has accepted share "/folderMain" offered by user "Alice"
     When user "Brian" searches for "SubFolder1" using the WebDAV API
     Then the HTTP status code should be "207"
     And the following headers should match these regular expressions
@@ -37,7 +36,6 @@ Feature: REPORT request to Shares space
 
   Scenario Outline: check the REPORT response of the found file
     Given using <dav-path-version> DAV path
-    And user "Brian" has accepted share "/folderMain" offered by user "Alice"
     And user "Alice" has uploaded file with content "Not all those who wander are lost." to "/folderMain/SubFolder1/subFOLDER2/frodo.txt"
     When user "Brian" searches for "frodo.txt" using the WebDAV API
     Then the HTTP status code should be "207"
@@ -59,8 +57,11 @@ Feature: REPORT request to Shares space
 
 
   Scenario Outline: search for the shared folder when share is not accepted
-    Given using <dav-path-version> DAV path
-    When user "Brian" searches for "folderMain" using the WebDAV API
+    Given user "Brian" has disabled auto-accepting
+    And using <dav-path-version> DAV path
+    And user "Alice" has created folder "/folderToBrian"
+    And user "Alice" has shared entry "/folderToBrian" with user "Brian" with permissions "17"
+    When user "Brian" searches for "folderToBrian" using the WebDAV API
     Then the HTTP status code should be "207"
     And the following headers should match these regular expressions
       | X-Request-Id | /^[a-zA-Z]+\/[a-zA-Z]+\.feature:\d+(-\d+)?$/ |

tests/acceptance/features/apiContract/spacesSharesReport.feature

@@ -24,7 +24,6 @@ Feature: Report test
       | path      | folderMain |
       | shareWith | Brian      |
       | role      | viewer     |
-    And user "Brian" has accepted share "/folderMain" offered by user "Alice"
     When user "Brian" searches for "SubFolder1" using the WebDAV API
     Then the HTTP status code should be "207"
     And the following headers should match these regular expressions
@@ -45,7 +44,6 @@ Feature: Report test
       | path      | folderMain |
       | shareWith | Brian      |
       | role      | editor     |
-    And user "Brian" has accepted share "/folderMain" offered by user "Alice"
     When user "Brian" searches for "insideTheFolder.txt" using the WebDAV API
     Then the HTTP status code should be "207"
     And the following headers should match these regular expressions
@@ -62,7 +60,8 @@ Feature: Report test
 
 
   Scenario: search for the shared folder when the share is not accepted
-    Given user "Alice" has created a share inside of space "find data" with settings:
+    Given user "Brian" has disabled auto-accepting
+    And user "Alice" has created a share inside of space "find data" with settings:
       | path      | folderMain |
       | shareWith | Brian      |
       | role      | viewer     |

tests/acceptance/features/apiGraph/deleteGroup.feature

@@ -83,7 +83,6 @@ Feature: delete groups
     And group "grp1" has been created
     And user "Brian" has been added to group "grp1"
     And user "Alice" has shared file "lorem.txt" with group "grp1"
-    And user "Brian" has accepted share "/lorem.txt" offered by user "Alice"
     When user "Alice" deletes group "grp1" using the Graph API
     Then the HTTP status code should be "204"
     And user "Brian" should not have any received shares

tests/acceptance/features/apiGraph/deleteUser.feature

@@ -161,7 +161,6 @@ Feature: delete user
       | path      | new    |
       | shareWith | Alice  |
       | role      | viewer |
-    And user "Alice" has accepted share "/new" offered by user "Brian"
     When the user "Alice" deletes a user "Brian" using the Graph API
     Then the HTTP status code should be "204"
     And as "Alice" folder "Shares/new" should not exist

tests/acceptance/features/apiGraph/enforcePasswordPublicLink.feature

@@ -245,11 +245,11 @@ Feature: enforce password on public link
 
 
   Scenario Outline: update a public link with a password that is listed in the Banned-Password-List
-    Given the config "FRONTEND_PASSWORD_POLICY_BANNED_PASSWORDS_LIST" has been set to path "bannedPassword/banned-password-list.txt"
+    Given the config "FRONTEND_PASSWORD_POLICY_BANNED_PASSWORDS_LIST" has been set to path "config/drone/banned-password-list.txt"
     And using OCS API version "2"
     And user "Alice" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file with content "test file" to "/testfile.txt"
-    And user "Alice" has created a public link share with settings
+    And user "Alice" has created a public link share with settings 
       | path        | /testfile.txt |
       | permissions | 1             |
     When user "Alice" updates the last public link share using the sharing API with
@@ -269,7 +269,7 @@ Feature: enforce password on public link
 
 
   Scenario Outline: create  a public link with a password that is listed in the Banned-Password-List
-    Given the config "FRONTEND_PASSWORD_POLICY_BANNED_PASSWORDS_LIST" has been set to path "bannedPassword/banned-password-list.txt"
+    Given the config "FRONTEND_PASSWORD_POLICY_BANNED_PASSWORDS_LIST" has been set to path "config/drone/banned-password-list.txt"
     And using OCS API version "2"
     And user "Alice" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file with content "test file" to "/testfile.txt"

tests/acceptance/features/apiNotification/notification.feature

@@ -128,7 +128,6 @@ Feature: Notification
 
   Scenario Outline: user gets a notification of unsharing resource
     Given user "Alice" has shared entry "<resource>" with user "Brian"
-    And user "Brian" has accepted share "/<resource>" offered by user "Alice"
     And user "Alice" has unshared entity "<resource>" shared to "Brian"
     When user "Brian" lists all notifications
     Then the HTTP status code should be "200"
@@ -295,7 +294,6 @@ Feature: Notification
 
   Scenario Outline: notifications related to a resource get deleted when the resource is deleted
     Given user "Alice" has shared entry "<resource>" with user "Brian"
-    And user "Brian" has accepted share "/<resource>" offered by user "Alice"
     And user "Alice" has unshared entity "<resource>" shared to "Brian"
     And user "Alice" has deleted entity "/<resource>"
     When user "Brian" lists all notifications

tests/acceptance/features/apiReshare/disableReshare.feature

@@ -40,7 +40,6 @@ Feature: share by disabling re-share
       | path      | test   |
       | shareWith | Brian  |
       | role      | <role> |
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     When user "Brian" creates a share inside of space "Shares" with settings:
       | path      | test   |
       | shareWith | Carol  |

tests/acceptance/features/apiReshare/resharing.feature

@@ -18,16 +18,12 @@ Feature: Resharing
       | Gina     |
     And user "Alice" has created folder "folder"
     And user "Alice" has shared folder "folder" with user "Brian" with permissions "31"
-    And user "Brian" has accepted share "/folder" offered by user "Alice"
     And user "Brian" has shared folder "Shares/folder" with user "Carol" with permissions "31"
-    And user "Carol" has accepted share "/folder" offered by user "Brian"
     And user "Carol" has shared folder "Shares/folder" with user "Damian" with permissions "17"
-    And user "Damian" has accepted share "/folder" offered by user "Carol"
 
 
   Scenario Outline: user should only be able to see direct outgoing shares not all the chain
     Given user "Brian" has shared folder "Shares/folder" with user "Fred" with permissions "17"
-    And user "Fred" has accepted share "/folder" offered by user "Brian"
     When user "<user>" gets all the shares inside the folder "Shares/folder" using the sharing API
     Then the OCS status code should be "100"
     And the HTTP status code should be "200"
@@ -62,7 +58,6 @@ Feature: Resharing
 
   Scenario Outline: editing reshares
     Given user "Carol" has shared folder "Shares/folder" with user "Fred" with permissions "17"
-    And user "Fred" has accepted share "/folder" offered by user "Carol"
     When user "<user>" updates the last share using the sharing API with
       | permissions | 31 |
     Then the OCS status code should be "<code>"
@@ -76,7 +71,6 @@ Feature: Resharing
 
   Scenario Outline: deleting reshares
     Given user "Carol" has shared folder "Shares/folder" with user "Gina" with permissions "17"
-    And user "Gina" has accepted share "/folder" offered by user "Carol"
     When user "<user>" deletes the last share using the sharing API
     Then the OCS status code should be "<code>"
     And as "Gina" folder "Shares/folder" <exists>
@@ -103,7 +97,6 @@ Feature: Resharing
   Scenario Outline: Resharing files with different permissions
     Given user "Alice" has uploaded file with content "Random data" to "/file.txt"
     And user "Alice" has shared file "/file.txt" with user "Brian" with permissions "<shareepermissions>"
-    And user "Brian" has accepted share "/file.txt" offered by user "Alice"
     When user "Brian" shares file "Shares/file.txt" with user "Fred" with permissions "<granteepermissions>" using the sharing API
     Then the OCS status code should be "<code>"
     Examples:
@@ -119,10 +112,8 @@ Feature: Resharing
     And the administrator has added a user "Fred" to the group "security department" using GraphApi
     When user "Brian" shares folder "Shares/folder" with group "security department" with permissions "<permissions>" using the sharing API
     Then the OCS status code should be "100"
-    When user "Ember" accepts share "/folder" offered by user "Brian" using the sharing API
-    Then user "Ember" <canUpload> able to upload file "filesForUpload/textfile.txt" to "/Shares/folder/textfile.txt"
-    When user "Fred" accepts share "/folder" offered by user "Brian" using the sharing API
-    Then user "Fred" <canUpload> able to upload file "filesForUpload/textfile.txt" to "/Shares/folder/textfile.txt"
+    And user "Ember" <canUpload> able to upload file "filesForUpload/textfile.txt" to "/Shares/folder/textfile.txt"
+    And user "Fred" <canUpload> able to upload file "filesForUpload/textfile.txt" to "/Shares/folder/textfile.txt"
     Examples:
       | permissions | canUpload     |
       | 17          | should not be |

tests/acceptance/features/apiSearch/apiSpaceSearch.feature

@@ -59,7 +59,6 @@ Feature: Search
       | path      | folderMain |
       | shareWith | Brian      |
       | role      | viewer     |
-    And user "Brian" has accepted share "/folderMain" offered by user "Alice"
     When user "Brian" searches for "*folder*" using the WebDAV API
     Then the HTTP status code should be "207"
     And the search result should contain "4" entries
@@ -91,7 +90,8 @@ Feature: Search
 
 
   Scenario Outline: user cannot find pending share
-    Given using <dav-path-version> DAV path
+    Given user "Brian" has disabled auto-accepting
+    And using <dav-path-version> DAV path
     And user "Alice" has created a share inside of space "find data" with settings:
       | path      | folderMain |
       | shareWith | Brian      |
@@ -116,7 +116,7 @@ Feature: Search
       | path      | folderMain |
       | shareWith | Brian      |
       | role      | viewer     |
-    And user "Brian" has declined share "/folderMain" offered by user "Alice"
+    And user "Brian" has declined share "/Shares/folderMain" offered by user "Alice"
     When user "Brian" searches for "*folder*" using the WebDAV API
     Then the HTTP status code should be "207"
     And the search result should contain "0" entries
@@ -181,7 +181,6 @@ Feature: Search
       | path      | folderMain |
       | shareWith | Brian      |
       | role      | viewer     |
-    And user "Brian" has accepted share "/folderMain" offered by user "Alice"
     When user "Brian" searches for "*folder*" inside folder "/folderMain" in space "Shares" using the WebDAV API
     Then the HTTP status code should be "207"
     And the search result of user "Brian" should contain only these entries:
@@ -227,7 +226,6 @@ Feature: Search
       | path      | foo    |
       | shareWith | Brian  |
       | role      | viewer |
-    And user "Brian" has accepted share "/foo" offered by user "Alice"
     When user "Brian" searches for "shared*" using the WebDAV API
     Then the HTTP status code should be "207"
     And the search result of user "Brian" should contain these entries:

tests/acceptance/features/apiSearch/contentSearch.feature

@@ -36,7 +36,6 @@ Feature: content search
     And user "Alice" has uploaded file with content "nepal want to say hello" to "uploadFolder/keywordAtLast.txt"
     And user "Alice" has uploaded file with content "Namaste nepal" to "uploadFolder/hello.txt"
     And user "Alice" has shared folder "/uploadFolder" with user "Brian"
-    And user "Brian" has accepted share "/uploadFolder" offered by user "Alice"
     When user "Brian" searches for "Content:hello" using the WebDAV API
     Then the HTTP status code should be "207"
     And the search result of user "Brian" should contain only these files:

tests/acceptance/features/apiSearch/dateSearch.feature

@@ -55,7 +55,6 @@ Feature: date search
     And user "Alice" has created folder "sharedFolder"
     And user "Alice" uploads a file "filesForUpload/textfile.txt" to "/sharedFolder/yesterday.txt" with mtime "yesterday" via TUS inside of the space "Personal" using the WebDAV API
     And user "Alice" has shared folder "/sharedFolder" with user "Brian"
-    And user "Brian" has accepted share "/sharedFolder" offered by user "Alice"
     When user "Brian" searches for "Mtime:yesterday" using the WebDAV API
     Then the HTTP status code should be "207"
     And the search result of user "Brian" should contain these entries:

tests/acceptance/features/apiSearch/tagSearch.feature

@@ -126,7 +126,6 @@ Feature: tag search
     And user "Alice" has created the following tags for file "uploadFolder/file1.txt" of the space "Personal":
       | tag1 |
     And user "Alice" has shared folder "/uploadFolder" with user "Brian"
-    And user "Brian" has accepted share "/uploadFolder" offered by user "Alice"
     And user "Brian" has created the following tags for file "uploadFolder/file2.txt" of the space "Shares":
       | tag1 |
     When user "Brian" searches for "Tags:tag1" using the WebDAV API

tests/acceptance/features/apiSpaces/listSpaces.feature

@@ -81,7 +81,6 @@ Feature: List and create spaces
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Brian" has created folder "folder"
     And user "Brian" has shared folder "folder" with user "Alice" with permissions "31"
-    And user "Alice" has accepted share "/folder" offered by user "Brian"
     When user "Alice" lists all available spaces via the GraphApi with query "$filter=driveType eq 'personal'"
     Then the HTTP status code should be "200"
     And the JSON response should contain space called "Alice Hansen" and match

tests/acceptance/features/apiSpaces/tag.feature

@@ -113,12 +113,6 @@ Feature: Tag
       | role      | viewer     |
     When user "Brian" lists all available tags via the GraphApi
     Then the HTTP status code should be "200"
-    And the response should not contain following tags:
-      | folderTag |
-      | marketing |
-    When user "Brian" accepts share "/folderMain" offered by user "Alice" using the sharing API
-    And user "Brian" lists all available tags via the GraphApi
-    Then the HTTP status code should be "200"
     And the response should contain following tags:
       | folderTag |
       | marketing |
@@ -129,7 +123,6 @@ Feature: Tag
       | path      | folderMain |
       | shareWith | Brian      |
       | role      | <role>     |
-    And user "Brian" has accepted share "/folderMain" offered by user "Alice"
     When user "Brian" creates the following tags for <resource> "<resourceName>" of space "Shares":
       | tag in a shared resource |
       | second tag               |
@@ -157,7 +150,6 @@ Feature: Tag
     And user "Alice" has created the following tags for <resource> "<resourceName>" of the space "use-tag":
       | tag in a shared resource |
       | second tag               |
-    And user "Brian" has accepted share "/folderMain" offered by user "Alice"
     When user "Brian" removes the following tags for <resource> "<resourceName>" of space "Shares":
       | tag in a shared resource |
       | second tag               |

tests/acceptance/features/apiSpacesDavOperation/getFileByFileId.feature

@@ -52,7 +52,6 @@ Feature: accessing files using file id
     And user "Alice" has uploaded file with content "some data" to "/textfile.txt"
     And we save it into "FILEID"
     And user "Alice" has shared file "/textfile.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile.txt" offered by user "Alice"
     When user "Brian" sends HTTP method "GET" to URL "<dav-path>"
     Then the HTTP status code should be "200"
     And the downloaded content should be "some data"
@@ -68,7 +67,6 @@ Feature: accessing files using file id
     And user "Alice" has uploaded file with content "some data" to "uploadFolder/textfile.txt"
     And we save it into "FILEID"
     And user "Alice" has shared folder "/uploadFolder" with user "Brian"
-    And user "Brian" has accepted share "/uploadFolder" offered by user "Alice"
     When user "Brian" sends HTTP method "GET" to URL "<dav-path>"
     Then the HTTP status code should be "200"
     And the downloaded content should be "some data"

tests/acceptance/features/apiSpacesDavOperation/propfindByFileId.feature

@@ -105,7 +105,6 @@ Feature: propfind a file using file id
     And user "Alice" has uploaded file with content "some data" to "/textfile.txt"
     And we save it into "FILEID"
     And user "Alice" has shared file "/textfile.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile.txt" offered by user "Alice"
     When user "Brian" sends HTTP method "PROPFIND" to URL "<dav-path>"
     Then the HTTP status code should be "207"
     And the "PROPFIND" response to user "Alice" should contain a mountpoint "Brian Murphy" with these key and value pairs:
@@ -122,7 +121,6 @@ Feature: propfind a file using file id
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/folder"
     And user "Alice" has shared folder "/folder" with user "Brian"
-    And user "Brian" has accepted share "/folder" offered by user "Alice"
     And user "Alice" has uploaded file with content "some data" to "/folder/textfile.txt"
     And we save it into "FILEID"
     When user "Brian" sends HTTP method "PROPFIND" to URL "<dav-path>"

tests/acceptance/features/apiSpacesDavOperation/updateFileByFileId.feature

@@ -52,7 +52,6 @@ Feature: update files using file id
     And user "Alice" has uploaded file with content "some data" to "/textfile.txt"
     And we save it into "FILEID"
     And user "Alice" has shared file "/textfile.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile.txt" offered by user "Alice"
     When user "Brian" sends HTTP method "PUT" to URL "<dav-path>" with content "updated content"
     Then the HTTP status code should be "204"
     And for user "Alice" the content of the file "/textfile.txt" of the space "Personal" should be "updated content"
@@ -69,7 +68,6 @@ Feature: update files using file id
     And user "Alice" has uploaded file with content "some data" to "uploadFolder/textfile.txt"
     And we save it into "FILEID"
     And user "Alice" has shared folder "/uploadFolder" with user "Brian"
-    And user "Brian" has accepted share "/uploadFolder" offered by user "Alice"
     When user "Brian" sends HTTP method "PUT" to URL "<dav-path>" with content "updated content"
     Then the HTTP status code should be "204"
     And for user "Alice" the content of the file "uploadFolder/textfile.txt" of the space "Personal" should be "updated content"

tests/acceptance/features/apiSpacesShares/changingFilesShare.feature

@@ -19,8 +19,6 @@ Feature: change shared resource
     And user "Alice" has moved file "textfile0.txt" to "PARENT/from_alice.txt" in space "Personal"
     And user "Alice" has shared folder "/PARENT" with user "Carol"
     And user "Brian" has shared folder "/PARENT" with user "Carol"
-    And user "Carol" has accepted share "/PARENT" offered by user "Alice"
-    And user "Carol" has accepted share "/PARENT" offered by user "Brian"
     When user "Carol" moves file "PARENT/from_alice.txt" to "PARENT (1)/from_alice.txt" in space "Shares" using the WebDAV API
     Then the HTTP status code should be "201"
     And for user "Carol" folder "PARENT" of the space "Shares" should not contain these entries:
@@ -34,7 +32,6 @@ Feature: change shared resource
     And user "Alice" has uploaded file with content "old content version 1" to "/textfile1.txt"
     And user "Alice" has uploaded file with content "old content version 2" to "/textfile1.txt"
     And user "Alice" has shared file "/textfile1.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile1.txt" offered by user "Alice"
     When user "Brian" uploads a file inside space "Shares" with content "this is a new content" to "textfile1.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And for user "Brian" the space "Shares" should contain these entries:

tests/acceptance/features/apiSpacesShares/checksum.feature

@@ -12,7 +12,6 @@ Feature: checksums
   Scenario: sharing a file with checksum should return the checksum in the propfind using new DAV path
     Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
     And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/myChecksumFile.txt" offered by user "Alice"
     When user "Brian" requests the checksum of file "/myChecksumFile.txt" in space "Shares" via propfind using the WebDAV API
     Then the HTTP status code should be "207"
     And the webdav checksum should match "SHA1:3ee962b839762adb0ad8ba6023a4690be478de6f MD5:d70b40f177b14b470d1756a3c12b963a ADLER32:8ae90960"
@@ -21,7 +20,6 @@ Feature: checksums
   Scenario: modifying a shared file should return correct checksum in the propfind using new DAV path
     Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
     And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/myChecksumFile.txt" offered by user "Alice"
     When user "Brian" uploads file with checksum "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399" and content "Some Text" to "/myChecksumFile.txt" in space "Shares" using the WebDAV API
     Then the HTTP status code should be "204"
     And as user "Alice" the webdav checksum of "/myChecksumFile.txt" via propfind should match "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a"

tests/acceptance/features/apiSpacesShares/copySpaces.feature

@@ -117,7 +117,6 @@ Feature: copy file
       | shareWith | Alice  |
       | role      | <role> |
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "31"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies file "/project.txt" from space "Project" to "/testshare/project.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "201"
     And for user "Alice" folder "testshare" of the space "Shares" should contain these files:
@@ -139,7 +138,6 @@ Feature: copy file
       | shareWith | Alice  |
       | role      | <role> |
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "17"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies file "/project.txt" from space "Project" to "/testshare/project.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "403"
     And for user "Alice" folder "testshare" of the space "Shares" should not contain these files:
@@ -185,7 +183,6 @@ Feature: copy file
   Scenario: user copies a file from personal space to share space with role editor
     Given user "Brian" has created folder "/testshare"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "31"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     And user "Alice" has uploaded file with content "personal content" to "personal.txt"
     When user "Alice" copies file "/personal.txt" from space "Personal" to "/testshare/personal.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "201"
@@ -197,7 +194,6 @@ Feature: copy file
   Scenario: user copies a file from personal space to share space with role viewer
     Given user "Brian" has created folder "/testshare"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "17"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     And user "Alice" has uploaded file with content "personal content" to "/personal.txt"
     When user "Alice" copies file "/personal.txt" from space "Personal" to "/testshare/personal.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "403"
@@ -210,7 +206,6 @@ Feature: copy file
     And user "Brian" has created folder "/testshare"
     And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies file "/testshare/testshare.txt" from space "Shares" to "/testshare.txt" inside space "Personal" using the WebDAV API
     Then the HTTP status code should be "201"
     And for user "Alice" the space "Personal" should contain these entries:
@@ -231,7 +226,6 @@ Feature: copy file
     And user "Brian" has created folder "/testshare"
     And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies file "/testshare/testshare.txt" from space "Shares" to "/testshare.txt" inside space "Project" using the WebDAV API
     Then the HTTP status code should be "201"
     And for user "Alice" the space "Project" should contain these entries:
@@ -254,7 +248,6 @@ Feature: copy file
     And user "Brian" has created folder "/testshare"
     And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies file "/testshare/testshare.txt" from space "Shares" to "/testshare.txt" inside space "Project" using the WebDAV API
     Then the HTTP status code should be "403"
     And for user "Alice" the space "Project" should not contain these entries:
@@ -271,8 +264,6 @@ Feature: copy file
     And user "Brian" has uploaded file with content "testshare1 content" to "/testshare1/testshare1.txt"
     And user "Brian" has shared folder "/testshare1" with user "Alice" with permissions "<permissions>"
     And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "31"
-    And user "Alice" has accepted share "/testshare1" offered by user "Brian"
-    And user "Alice" has accepted share "/testshare2" offered by user "Brian"
     When user "Alice" copies file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "201"
     And for user "Alice" folder "testshare2" of the space "Shares" should contain these files:
@@ -293,8 +284,6 @@ Feature: copy file
     And user "Brian" has uploaded file with content "testshare1 content" to "/testshare1/testshare1.txt"
     And user "Brian" has shared folder "/testshare1" with user "Alice" with permissions "<permissions>"
     And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "17"
-    And user "Alice" has accepted share "/testshare1" offered by user "Brian"
-    And user "Alice" has accepted share "/testshare2" offered by user "Brian"
     When user "Alice" copies file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "403"
     And for user "Alice" folder "testshare2" of the space "Shares" should not contain these files:
@@ -383,7 +372,6 @@ Feature: copy file
       | shareWith | Alice  |
       | role      | <role> |
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies folder "/folder1" from space "Project" to "/testshare/folder1" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "<status-code>"
     And for user "Alice" folder "<parent-folder>" of the space "Shares" <shouldOrNot> contain these files:
@@ -420,7 +408,6 @@ Feature: copy file
   Scenario Outline: user copies a folder from personal space to share space with different permissions
     Given user "Brian" has created folder "/testshare"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     And user "Alice" has created folder "folder1"
     And user "Alice" has uploaded file with content "some content" to "folder1/demo.txt"
     When user "Alice" copies folder "/folder1" from space "Personal" to "/testshare/folder1" inside space "Shares" using the WebDAV API
@@ -438,7 +425,6 @@ Feature: copy file
     And user "Brian" has created folder "/testshare"
     And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies file "/testshare/testshare.txt" from space "Shares" to "/testshare.txt" inside space "Personal" using the WebDAV API
     Then the HTTP status code should be "201"
     And for user "Alice" the space "Personal" should contain these entries:
@@ -460,7 +446,6 @@ Feature: copy file
     And user "Brian" has created folder "/testshare/folder1"
     And user "Brian" has uploaded file with content "testshare content" to "/testshare/folder1/testshare.txt"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies folder "/testshare/folder1" from space "Shares" to "folder1" inside space "Project" using the WebDAV API
     Then the HTTP status code should be "201"
     And for user "Alice" folder "folder1" of the space "Project" should contain these files:
@@ -483,7 +468,6 @@ Feature: copy file
     And user "Brian" has created folder "/testshare/folder1"
     And user "Brian" has uploaded file with content "testshare content" to "/testshare/folder1/testshare.txt"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies folder "/testshare/folder1" from space "Shares" to "folder1" inside space "Project" using the WebDAV API
     Then the HTTP status code should be "403"
     And for user "Alice" folder "/" of the space "Project" should not contain these files:
@@ -502,7 +486,6 @@ Feature: copy file
       | shareType   | user      |
       | permissions | read      |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     When user "Alice" copies file "/textfile0.txt" from space "Personal" to "/testshare/textfile0.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "403"
@@ -519,7 +502,6 @@ Feature: copy file
       | shareType   | user      |
       | permissions | read      |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies file "/textfile0.txt" from space "Personal" to "/testshare/overwritethis.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "403"
     And for user "Alice" the content of the file "/testshare/overwritethis.txt" of the space "Shares" should be "ownCloud test text file 1"
@@ -531,7 +513,6 @@ Feature: copy file
     And user "Brian" has created folder "/BRIAN-Folder"
     And user "Brian" has created folder "BRIAN-Folder/sample-folder"
     And user "Brian" has shared folder "BRIAN-Folder" with user "Alice"
-    And user "Alice" has accepted share "/BRIAN-Folder" offered by user "Brian"
     When user "Alice" copies file "/textfile1.txt" from space "Personal" to "/BRIAN-Folder" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "204"
     And for user "Alice" the content of the file "/BRIAN-Folder" of the space "Shares" should be "ownCloud test text file 1"
@@ -545,7 +526,6 @@ Feature: copy file
     And user "Alice" has created folder "/FOLDER/sample-folder"
     And user "Brian" has uploaded file with content "file to share" to "/sharedfile1.txt"
     And user "Brian" has shared file "/sharedfile1.txt" with user "Alice"
-    And user "Alice" has accepted share "/sharedfile1.txt" offered by user "Brian"
     When user "Alice" copies folder "/FOLDER" from space "Personal" to "/sharedfile1.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "204"
     And as "Alice" folder "/FOLDER/sample-folder" should exist
@@ -560,7 +540,6 @@ Feature: copy file
     And user "Brian" has created folder "/BRIAN-FOLDER/second-level-folder"
     And user "Brian" has created folder "/BRIAN-FOLDER/second-level-folder/third-level-folder"
     And user "Brian" has shared folder "/BRIAN-FOLDER" with user "Alice"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "/Sample-Folder-A"
     And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b"
     And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b/sample-folder-c"
@@ -581,7 +560,6 @@ Feature: copy file
     And user "Brian" has created folder "/BRIAN-FOLDER/second-level-folder"
     And user "Brian" has created folder "/BRIAN-FOLDER/second-level-folder/third-level-folder"
     And user "Brian" has shared folder "/BRIAN-FOLDER" with user "Alice"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "/Sample-Folder-A"
     And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b"
     And user "Alice" has uploaded file with content "sample file-c" to "/Sample-Folder-A/sample-folder-b/textfile-c.txt"
@@ -603,7 +581,6 @@ Feature: copy file
     And user "Brian" has created folder "/BRIAN-FOLDER"
     And user "Brian" has uploaded file with content "file at second level" to "/BRIAN-FOLDER/second-level-file.txt"
     And user "Brian" has shared folder "/BRIAN-FOLDER" with user "Alice"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "/Sample-Folder-A"
     And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b"
     And user "Alice" has uploaded file with content "sample file-c" to "/Sample-Folder-A/sample-folder-b/textfile-c.txt"
@@ -629,7 +606,6 @@ Feature: copy file
     And user "Brian" has created folder "/BRIAN-FOLDER/second-level-folder"
     And user "Brian" has uploaded file with content "file at third level" to "BRIAN-FOLDER/second-level-folder/third-level-file.txt"
     And user "Brian" has shared folder "/BRIAN-FOLDER" with user "Alice"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     When user "Alice" copies folder "/FOLDER/second-level-folder" from space "Personal" to "/BRIAN-FOLDER/second-level-folder/third-level-file.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "204"
     And for user "Alice" folder "BRIAN-FOLDER/second-level-folder/third-level-file.txt" of the space "Shares" should contain these entries:
@@ -649,7 +625,6 @@ Feature: copy file
     And user "Brian" has created folder "/BRIAN-FOLDER/second-level-folder"
     And user "Brian" has created folder "/BRIAN-FOLDER/second-level-folder/third-level-folder"
     And user "Brian" has shared folder "/BRIAN-FOLDER" with group "grp1"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "/Sample-Folder-A"
     And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b"
     And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b/sample-folder-c"
@@ -671,7 +646,6 @@ Feature: copy file
     And user "Brian" has created folder "/BRIAN-FOLDER/second-level-folder"
     And user "Brian" has created folder "/BRIAN-FOLDER/second-level-folder/third-level-folder"
     And user "Brian" has shared folder "/BRIAN-FOLDER" with group "grp1"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "/Sample-Folder-A"
     And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b"
     And user "Alice" has uploaded file with content "sample file-c" to "/Sample-Folder-A/sample-folder-b/textfile-c.txt"
@@ -693,7 +667,6 @@ Feature: copy file
     And user "Brian" has created folder "BRIAN-FOLDER"
     And user "Brian" has uploaded file with content "file at second level" to "/BRIAN-FOLDER/second-level-file.txt"
     And user "Brian" has shared folder "/BRIAN-FOLDER" with group "grp1"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "/Sample-Folder-A"
     And user "Alice" has created folder "/Sample-Folder-A/sample-folder-b"
     And user "Alice" has uploaded file with content "sample file-c" to "/Sample-Folder-A/sample-folder-b/textfile-c.txt"
@@ -718,7 +691,6 @@ Feature: copy file
     And user "Brian" has created folder "/BRIAN-FOLDER/second-level-folder"
     And user "Brian" has uploaded file with content "file at third level" to "/BRIAN-FOLDER/second-level-folder/third-level-file.txt"
     And user "Brian" has shared folder "/BRIAN-FOLDER" with group "grp1"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has created folder "/FOLDER/second-level-folder"
     And user "Alice" has created folder "/FOLDER/second-level-folder/third-level-folder"
@@ -777,7 +749,6 @@ Feature: copy file
       | path      | newfolder |
       | shareWith | Brian     |
       | role      | editor    |
-    And user "Brian" has accepted share "/newfolder" offered by user "Alice"
     And user "Brian" has uploaded file with content "new content" to "/personal.txt"
     When user "Brian" copies file "/personal.txt" from space "Personal" to "/newfolder/personal (1).txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "201"
@@ -800,7 +771,6 @@ Feature: copy file
       | path      | newfolder |
       | shareWith | Brian     |
       | role      | editor    |
-    And user "Brian" has accepted share "/newfolder" offered by user "Alice"
     And user "Brian" has uploaded file with content "new content" to "/personal.txt"
     When user "Brian" overwrites file "/personal.txt" from space "Personal" to "/newfolder/personal.txt" inside space "Shares" while copying using the WebDAV API
     Then the HTTP status code should be "204"

tests/acceptance/features/apiSpacesShares/createFileFolderWhenSharesSpaceExist.feature

@@ -10,7 +10,6 @@ Feature: create file or folder named similar to Shares folder
       | Brian    |
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "read,update"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
 
 
   Scenario Outline: create a folder with a name similar to Shares

tests/acceptance/features/apiSpacesShares/etagPropagation.feature

@@ -15,7 +15,6 @@ Feature: check etag propagation after different file alterations
   Scenario: copying a file inside a folder as a share receiver changes its etag for all collaborators
     Given user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/upload/file.txt" inside space "Personal"
@@ -43,7 +42,6 @@ Feature: check etag propagation after different file alterations
   Scenario: copying a file inside a folder as a sharer changes its etag for all collaborators
     Given user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/upload/file.txt" inside space "Personal"
@@ -71,7 +69,6 @@ Feature: check etag propagation after different file alterations
   Scenario: share receiver renaming a file inside a folder changes its etag for all collaborators
     Given user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Personal"
@@ -95,7 +92,6 @@ Feature: check etag propagation after different file alterations
   Scenario: sharer renaming a file inside a folder changes its etag for all collaborators
     Given user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/upload/file.txt" on path "/upload/renamed.txt" inside space "Personal"
@@ -120,9 +116,7 @@ Feature: check etag propagation after different file alterations
     Given user "Alice" has created folder "/dst"
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has shared folder "/dst" with user "Brian"
-    And user "Brian" has accepted share "/dst" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/dst" inside space "Personal"
@@ -146,9 +140,7 @@ Feature: check etag propagation after different file alterations
     Given user "Alice" has created folder "/dst"
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has shared folder "/dst" with user "Brian"
-    And user "Brian" has accepted share "/dst" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/dst" inside space "Personal"
@@ -171,9 +163,7 @@ Feature: check etag propagation after different file alterations
     Given user "Alice" has created folder "/dst"
     And user "Alice" has created folder "/upload/toMove"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has shared folder "/dst" with user "Brian"
-    And user "Brian" has accepted share "/dst" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/dst" inside space "Personal"
@@ -196,9 +186,7 @@ Feature: check etag propagation after different file alterations
     Given user "Alice" has created folder "/dst"
     And user "Alice" has created folder "/upload/toMove"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has shared folder "/dst" with user "Brian"
-    And user "Brian" has accepted share "/dst" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/dst" inside space "Personal"
@@ -219,7 +207,6 @@ Feature: check etag propagation after different file alterations
 
   Scenario: share receiver creating a folder inside a folder received as a share changes its etag for all collaborators
     Given user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Brian" has stored etag of element "/" inside space "Shares"
@@ -236,7 +223,6 @@ Feature: check etag propagation after different file alterations
 
   Scenario: sharer creating a folder inside a shared folder changes etag for all collaborators
     Given user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Brian" has stored etag of element "/" inside space "Shares"
@@ -253,7 +239,6 @@ Feature: check etag propagation after different file alterations
 
   Scenario: share receiver uploading a file inside a folder received as a share changes its etag for all collaborators
     Given user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Brian" has stored etag of element "/" inside space "Shares"
@@ -270,7 +255,6 @@ Feature: check etag propagation after different file alterations
 
   Scenario: sharer uploading a file inside a shared folder should update etags for all collaborators
     Given user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Brian" has stored etag of element "/" inside space "Shares"
@@ -288,7 +272,6 @@ Feature: check etag propagation after different file alterations
   Scenario: share receiver overwriting a file inside a received shared folder should update etags for all collaborators
     Given user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Brian" has stored etag of element "/" inside space "Shares"
@@ -306,7 +289,6 @@ Feature: check etag propagation after different file alterations
   Scenario: sharer overwriting a file inside a shared folder should update etags for all collaborators
     Given user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Brian" has stored etag of element "/" inside space "Shares"
@@ -325,7 +307,6 @@ Feature: check etag propagation after different file alterations
     Given user "Alice" has created folder "/upload/sub"
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/sub/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/upload/sub" inside space "Personal"
@@ -352,7 +333,6 @@ Feature: check etag propagation after different file alterations
     Given user "Alice" has created folder "/upload/sub"
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/sub/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/upload/sub" inside space "Personal"
@@ -379,7 +359,6 @@ Feature: check etag propagation after different file alterations
     Given user "Alice" has created folder "/upload/sub"
     And user "Alice" has created folder "/upload/sub/toDelete"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/upload/sub" inside space "Personal"
@@ -406,7 +385,6 @@ Feature: check etag propagation after different file alterations
     Given user "Alice" has created folder "/upload/sub"
     And user "Alice" has created folder "/upload/sub/toDelete"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/" inside space "Personal"
     And user "Alice" has stored etag of element "/upload" inside space "Personal"
     And user "Alice" has stored etag of element "/upload/sub" inside space "Personal"

tests/acceptance/features/apiSpacesShares/favorite.feature

@@ -14,7 +14,6 @@ Feature: favorite
 
   Scenario: favorite a received share itself
     Given user "Alice" has shared folder "/PARENT" with user "Brian"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" favorites element "/PARENT" in space "Shares" using the WebDAV API
     Then the HTTP status code should be "207"
     And as user "Brian" folder "/PARENT" inside space "Shares" should be favorited
@@ -23,7 +22,6 @@ Feature: favorite
   Scenario: favorite a file inside of a received share
     Given user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
     And user "Alice" has shared folder "/PARENT" with user "Brian"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" favorites element "/PARENT/parent.txt" in space "Shares" using the WebDAV API
     Then the HTTP status code should be "207"
     And as user "Brian" file "/PARENT/parent.txt" inside space "Shares" should be favorited
@@ -32,7 +30,6 @@ Feature: favorite
   Scenario: favorite a folder inside of a received share
     Given user "Alice" has created folder "/PARENT/sub-folder"
     And user "Alice" has shared folder "/PARENT" with user "Brian"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" favorites element "/PARENT/sub-folder" in space "Shares" using the WebDAV API
     Then the HTTP status code should be "207"
     And as user "Brian" folder "/PARENT/sub-folder" inside space "Shares" should be favorited
@@ -41,7 +38,6 @@ Feature: favorite
   Scenario: sharee file favorite state should not change the favorite state of sharer
     Given user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
     And user "Alice" has shared file "/PARENT/parent.txt" with user "Brian"
-    And user "Brian" has accepted share "/parent.txt" offered by user "Alice"
     When user "Brian" favorites element "/parent.txt" in space "Shares" using the WebDAV API
     Then the HTTP status code should be "207"
     And as user "Brian" file "/parent.txt" inside space "Shares" should be favorited

tests/acceptance/features/apiSpacesShares/moveSpaces.feature

@@ -106,7 +106,6 @@ Feature: move (rename) file
       | shareWith | Alice  |
       | role      | <role> |
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" moves file "project.txt" from space "Project" to "/testshare/project.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "502"
     And for user "Alice" the space "Project" should contain these entries:
@@ -146,7 +145,6 @@ Feature: move (rename) file
   Scenario Outline: user moves a file from space personal to space Shares with different role (permission)
     Given user "Brian" has created folder "/testshare"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     And user "Alice" has uploaded file with content "personal content" to "personal.txt"
     When user "Alice" moves file "personal.txt" from space "Personal" to "/testshare/personal.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "502"
@@ -165,7 +163,6 @@ Feature: move (rename) file
     Given user "Brian" has created folder "/testshare"
     And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" moves file "/testshare/testshare.txt" from space "Shares" to "testshare.txt" inside space "Personal" using the WebDAV API
     Then the HTTP status code should be "502"
     And for user "Alice" the space "Personal" should not contain these entries:
@@ -188,7 +185,6 @@ Feature: move (rename) file
     And user "Brian" has created folder "/testshare"
     And user "Brian" has uploaded file with content "testshare content" to "/testshare/testshare.txt"
     And user "Brian" has shared folder "/testshare" with user "Alice" with permissions "<permissions>"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" moves file "/testshare/testshare.txt" from space "Shares" to "testshare.txt" inside space "Project" using the WebDAV API
     Then the HTTP status code should be "502"
     And for user "Alice" the space "Project" should not contain these entries:
@@ -211,8 +207,6 @@ Feature: move (rename) file
     And user "Brian" has uploaded file with content "testshare1 content" to "/testshare1/testshare1.txt"
     And user "Brian" has shared folder "/testshare1" with user "Alice" with permissions "31"
     And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "31"
-    And user "Alice" has accepted share "/testshare1" offered by user "Brian"
-    And user "Alice" has accepted share "/testshare2" offered by user "Brian"
     When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "201"
     And for user "Alice" folder "testshare2" of the space "Shares" should contain these entries:
@@ -229,8 +223,6 @@ Feature: move (rename) file
     And user "Brian" has uploaded file with content "testshare1 content" to "/testshare1/testshare1.txt"
     And user "Brian" has shared folder "/testshare1" with user "Alice" with permissions "31"
     And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "17"
-    And user "Alice" has accepted share "/testshare1" offered by user "Brian"
-    And user "Alice" has accepted share "/testshare2" offered by user "Brian"
     When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "403"
     And for user "Alice" folder "testshare2" of the space "Shares" should not contain these entries:
@@ -245,8 +237,6 @@ Feature: move (rename) file
     And user "Brian" has uploaded file with content "testshare1 content" to "/testshare1/testshare1.txt"
     And user "Brian" has shared folder "/testshare1" with user "Alice" with permissions "17"
     And user "Brian" has shared folder "/testshare2" with user "Alice" with permissions "31"
-    And user "Alice" has accepted share "/testshare1" offered by user "Brian"
-    And user "Alice" has accepted share "/testshare2" offered by user "Brian"
     When user "Alice" moves file "/testshare1/testshare1.txt" from space "Shares" to "/testshare2/testshare1.txt" inside space "Shares" using the WebDAV API
     Then the HTTP status code should be "403"
     And for user "Alice" folder "testshare2" of the space "Shares" should not contain these entries:
@@ -262,8 +252,6 @@ Feature: move (rename) file
       | /folderB |
     And user "Alice" has shared folder "/folderA" with user "Brian"
     And user "Alice" has shared folder "/folderB" with user "Brian"
-    And user "Brian" has accepted share "/folderA" offered by user "Alice"
-    And user "Brian" has accepted share "/folderB" offered by user "Alice"
     And user "Brian" has created a folder "/folderA/ONE" in space "Shares"
     And user "Brian" has created a folder "/folderA/ONE/TWO" in space "Shares"
     And user "Brian" has stored id of folder "/folderA/ONE" of the space "Shares"
@@ -286,7 +274,6 @@ Feature: move (rename) file
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Brian" moves file "/testshare/testfile.txt" from space "Personal" to "/testfile.txt" inside space "Personal" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/testfile.txt" for user "Brian" should be "test data"
@@ -307,7 +294,6 @@ Feature: move (rename) file
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Brian" moves folder "/testshare/testsubfolder" from space "Personal" to "/testsubfolder" inside space "Personal" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/testsubfolder/testfile.txt" for user "Brian" should be "test data"

tests/acceptance/features/apiSpacesShares/shareOperations.feature

@@ -15,7 +15,6 @@ Feature: sharing
   Scenario: correct webdav share-permissions for received file with edit and reshare permissions
     Given user "Alice" has uploaded file with content "foo" to "/tmp.txt"
     And user "Alice" has shared file "/tmp.txt" with user "Brian"
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -32,7 +31,6 @@ Feature: sharing
       | shareType   | group             |
       | permissions | share,update,read |
       | shareWith   | grp1              |
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -43,7 +41,6 @@ Feature: sharing
   Scenario: correct webdav share-permissions for received file with edit permissions but no reshare permissions
     Given user "Alice" has uploaded file with content "foo" to "/tmp.txt"
     And user "Alice" has shared file "tmp.txt" with user "Brian"
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | update,read |
     Then the HTTP status code should be "200"
@@ -59,7 +56,6 @@ Feature: sharing
       | shareType   | group       |
       | permissions | update,read |
       | shareWith   | grp1        |
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -70,7 +66,6 @@ Feature: sharing
   Scenario: correct webdav share-permissions for received file with reshare permissions but no edit permissions
     Given user "Alice" has uploaded file with content "foo" to "/tmp.txt"
     And user "Alice" has shared file "tmp.txt" with user "Brian"
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,read |
     Then the HTTP status code should be "200"
@@ -86,7 +81,6 @@ Feature: sharing
       | shareType   | group      |
       | permissions | share,read |
       | shareWith   | grp1       |
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Brian" gets the following properties of file "/tmp.txt" inside space "Shares" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -97,7 +91,6 @@ Feature: sharing
   Scenario: correct webdav share-permissions for received folder with all permissions
     Given user "Alice" has created folder "/tmp"
     And user "Alice" has shared file "/tmp" with user "Brian"
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -113,7 +106,6 @@ Feature: sharing
       | path      | tmp   |
       | shareType | group |
       | shareWith | grp1  |
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -124,7 +116,6 @@ Feature: sharing
   Scenario: correct webdav share-permissions for received folder with all permissions but edit
     Given user "Alice" has created folder "/tmp"
     And user "Alice" has shared file "/tmp" with user "Brian"
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,delete,create,read |
     Then the HTTP status code should be "200"
@@ -140,7 +131,6 @@ Feature: sharing
       | shareType   | group                    |
       | shareWith   | grp1                     |
       | permissions | share,delete,create,read |
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -151,7 +141,6 @@ Feature: sharing
   Scenario: correct webdav share-permissions for received folder with all permissions but create
     Given user "Alice" has created folder "/tmp"
     And user "Alice" has shared file "/tmp" with user "Brian"
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,delete,update,read |
     Then the HTTP status code should be "200"
@@ -167,7 +156,6 @@ Feature: sharing
       | shareType   | group                    |
       | shareWith   | grp1                     |
       | permissions | share,delete,update,read |
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -178,7 +166,6 @@ Feature: sharing
   Scenario: correct webdav share-permissions for received folder with all permissions but delete
     Given user "Alice" has created folder "/tmp"
     And user "Alice" has shared file "/tmp" with user "Brian"
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,create,update,read |
     Then the HTTP status code should be "200"
@@ -194,7 +181,6 @@ Feature: sharing
       | shareType   | group                    |
       | shareWith   | grp1                     |
       | permissions | share,create,update,read |
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -205,7 +191,6 @@ Feature: sharing
   Scenario: correct webdav share-permissions for received folder with all permissions but share
     Given user "Alice" has created folder "/tmp"
     And user "Alice" has shared file "/tmp" with user "Brian"
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | change |
     Then the HTTP status code should be "200"
@@ -221,7 +206,6 @@ Feature: sharing
       | shareType   | group  |
       | shareWith   | grp1   |
       | permissions | change |
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/tmp" inside space "Shares" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -238,7 +222,6 @@ Feature: sharing
       | shareType   | group  |
       | permissions | read   |
       | shareWith   | grp1   |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "403"
     And as "Alice" file "/FOLDER/textfile.txt" should not exist
@@ -251,7 +234,6 @@ Feature: sharing
       | shareType   | user   |
       | permissions | create |
       | shareWith   | Brian  |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the following headers should match these regular expressions for user "Brian"
@@ -271,7 +253,6 @@ Feature: sharing
       | shareType   | group  |
       | permissions | create |
       | shareWith   | grp1   |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the following headers should match these regular expressions for user "Brian"
@@ -289,7 +270,6 @@ Feature: sharing
       | shareType   | user   |
       | permissions | change |
       | shareWith   | Brian  |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/FOLDER/textfile.txt" for user "Alice" should be:
@@ -307,7 +287,6 @@ Feature: sharing
       | shareType   | group  |
       | permissions | change |
       | shareWith   | grp1   |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/FOLDER/textfile.txt" for user "Alice" should be:
@@ -323,7 +302,6 @@ Feature: sharing
       | shareType   | user   |
       | permissions | change |
       | shareWith   | Brian  |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1"
     When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "507"
@@ -337,7 +315,6 @@ Feature: sharing
       | shareType   | user   |
       | permissions | create |
       | shareWith   | Brian  |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "1"
     When user "Brian" uploads a file inside space "Shares" with content "new description" to "/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "507"
@@ -353,7 +330,6 @@ Feature: sharing
       | shareType   | group  |
       | permissions | create |
       | shareWith   | grp1   |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Admin" has changed the quota of the personal space of "Alice Hansen" space to "10"
     When user "Brian" uploads a file inside space "Shares" with content "new descriptionfgshsywhhh" to "/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "507"
@@ -367,7 +343,6 @@ Feature: sharing
       | shareType   | user          |
       | permissions | <permissions> |
       | shareWith   | Brian         |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads a file inside space "Shares" with content "some content" to "/FOLDER/textfile.txt" using the WebDAV API
     And user "Alice" downloads file "/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "200"

tests/acceptance/features/apiSpacesShares/shareSubItemOfSpace.feature

@@ -29,8 +29,7 @@ Feature: Share a file or folder that is inside a space
     Then the HTTP status code should be "200"
     And the OCS status code should be "200"
     And the OCS status message should be "OK"
-    When user "Brian" accepts share "/<entity>" offered by user "Alice" using the sharing API
-    Then as "Brian" <type> "Shares/<entity>" should exist
+    And as "Brian" <type> "Shares/<entity>" should exist
     And the information about the last share for user "Brian" should include
       | expiration | <expiration> |
     Examples:
@@ -53,8 +52,7 @@ Feature: Share a file or folder that is inside a space
     Then the HTTP status code should be "200"
     And the OCS status code should be "200"
     And the OCS status message should be "OK"
-    When user "Bob" accepts share "/<entity>" offered by user "Brian" using the sharing API
-    Then as "Bob" <type> "Shares/<entity>" should exist
+    And as "Bob" <type> "Shares/<entity>" should exist
     And the information about the last share for user "Brian" should include
       | expiration | <expiration> |
     Examples:
@@ -113,8 +111,7 @@ Feature: Share a file or folder that is inside a space
     Then the HTTP status code should be "200"
     And the OCS status code should be "200"
     And the OCS status message should be "OK"
-    When user "Brian" accepts share "/folder" offered by user "Alice" using the sharing API
-    Then as "Brian" folder "Shares/folder" should exist
+    And as "Brian" folder "Shares/folder" should exist
     And the information about the last share for user "Brian" should include
       | expiration | 2042-01-01 |
 
@@ -125,7 +122,6 @@ Feature: Share a file or folder that is inside a space
       | shareWith  | Brian                    |
       | role       | viewer                   |
       | expireDate | 2042-01-01T23:59:59+0100 |
-    And user "Brian" has accepted share "/folder" offered by user "Alice"
     When user "Alice" changes the last share with settings:
       | expireDate | 2044-01-01T23:59:59.999+01:00 |
     Then the HTTP status code should be "200"
@@ -139,7 +135,6 @@ Feature: Share a file or folder that is inside a space
       | shareWith  | Brian                    |
       | role       | viewer                   |
       | expireDate | 2042-01-01T23:59:59+0100 |
-    And user "Brian" has accepted share "/folder" offered by user "Alice"
     When user "Alice" changes the last share with settings:
       | expireDate |  |
     Then the HTTP status code should be "200"
@@ -153,7 +148,6 @@ Feature: Share a file or folder that is inside a space
       | shareWith  | Brian                    |
       | role       | viewer                   |
       | expireDate | 2042-01-01T23:59:59+0100 |
-    And user "Brian" has accepted share "/folder" offered by user "Alice"
     When user "Alice" expires the last share
     Then the HTTP status code should be "200"
     And as "Brian" folder "Shares/folder" should not exist
@@ -168,7 +162,6 @@ Feature: Share a file or folder that is inside a space
       | shareType  | 1                        |
       | role       | viewer                   |
       | expireDate | 2042-01-01T23:59:59+0100 |
-    And user "Brian" has accepted share "/folder" offered by user "Alice"
     When user "Alice" expires the last share
     Then the HTTP status code should be "200"
     And as "Brian" folder "Shares/folder" should not exist

tests/acceptance/features/apiSpacesShares/shareUploadTUS.feature

@@ -14,7 +14,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: upload file with mtime to a received share
     Given user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     When user "Brian" uploads a file "filesForUpload/textfile.txt" to "toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" via TUS inside of the space "Shares" using the WebDAV API
     Then for user "Brian" folder "toShare" of the space "Shares" should contain these entries:
       | file.txt |
@@ -25,7 +24,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: upload file with mtime to a sent share
     Given user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     When user "Alice" uploads a file "filesForUpload/textfile.txt" to "toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" via TUS inside of the space "Personal" using the WebDAV API
     Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries:
       | file.txt |
@@ -36,7 +34,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: overwriting a file with mtime in a received share
     Given user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     And user "Alice" has uploaded file with content "uploaded content" to "/toShare/file.txt"
     When user "Brian" uploads a file "filesForUpload/textfile.txt" to "toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" via TUS inside of the space "Shares" using the WebDAV API
     Then for user "Brian" folder "toShare" of the space "Shares" should contain these entries:
@@ -48,7 +45,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: overwriting a file with mtime in a sent share
     Given user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     And user "Brian" has uploaded a file inside space "Shares" with content "uploaded content" to "toShare/file.txt"
     When user "Alice" uploads a file "filesForUpload/textfile.txt" to "toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" via TUS inside of the space "Personal" using the WebDAV API
     Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries:
@@ -61,7 +57,6 @@ Feature: upload resources on share using TUS protocol
     Given using OCS API version "1"
     And user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     When user "Brian" uploads a file with content "uploaded content" to "/toShare/nonExistentFolder/file.txt" via TUS inside of the space "Shares" using the WebDAV API
     Then for user "Brian" folder "toShare" of the space "Shares" should not contain these entries:
       | nonExistentFolder |
@@ -71,7 +66,6 @@ Feature: upload resources on share using TUS protocol
     Given using OCS API version "1"
     And user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian" with permissions "read"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     When user "Brian" uploads a file with content "uploaded content" to "/toShare/nonExistentFolder/file.txt" via TUS inside of the space "Shares" using the WebDAV API
     Then for user "Brian" folder "toShare" of the space "Shares" should not contain these entries:
       | nonExistentFolder |
@@ -80,7 +74,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: uploading a file to a received share folder
     Given user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares" using the WebDAV API
     Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries:
       | file.txt |
@@ -90,7 +83,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: uploading a file to a user read/write share folder
     Given user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian" with permissions "change"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares" using the WebDAV API
     Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries:
       | file.txt |
@@ -102,7 +94,6 @@ Feature: upload resources on share using TUS protocol
     And user "Brian" has been added to group "grp1"
     And user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "toShare" with group "grp1" with permissions "change"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares" using the WebDAV API
     Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries:
       | file.txt |
@@ -113,7 +104,6 @@ Feature: upload resources on share using TUS protocol
     Given user "Alice" has created folder "/toShare"
     And user "Alice" has uploaded file with content "original content" to "/toShare/file.txt"
     And user "Alice" has shared folder "/toShare" with user "Brian"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     When user "Brian" uploads a file with content "overwritten content" to "/toShare/file.txt" via TUS inside of the space "Shares" using the WebDAV API
     Then for user "Alice" folder "toShare" of the space "Personal" should contain these entries:
       | file.txt |
@@ -123,7 +113,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: attempt to upload a file into a folder within correctly received read only share
     Given user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian" with permissions "read"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     When user "Brian" uploads a file with content "uploaded content" to "/toShare/file.txt" via TUS inside of the space "Shares" using the WebDAV API
     Then for user "Brian" folder "toShare" of the space "Shares" should not contain these entries:
       | file.txt |
@@ -132,7 +121,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: upload a file to shared folder with checksum should return the checksum in the propfind for sharee
     Given user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Alice" has created a new TUS resource for the space "Personal" with content "" using the WebDAV API with these headers:
       | Upload-Length   | 5                                     |
       #    L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt
@@ -147,7 +135,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: upload a file to shared folder with checksum should return the checksum in the download header for sharee
     Given user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Alice" has created a new TUS resource for the space "Personal" with content "" using the WebDAV API with these headers:
       | Upload-Length   | 5                                     |
       #    L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt
@@ -166,7 +153,6 @@ Feature: upload resources on share using TUS protocol
       | Tus-Resumable   | 1.0.0                     |
     And user "Alice" has uploaded file with checksum "SHA1 8cb2237d0679ca88db6464eac60da96345513964" to the last created TUS Location with offset "0" and content "12345" via TUS inside of the space "Personal" using the WebDAV API
     And user "Alice" has shared file "/textFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/textFile.txt" offered by user "Alice"
     When user "Brian" requests the checksum of file "/textFile.txt" in space "Shares" via propfind using the WebDAV API
     Then the HTTP status code should be "207"
     And the webdav checksum should match "SHA1:8cb2237d0679ca88db6464eac60da96345513964 MD5:827ccb0eea8a706c4c34a16891f84e7b ADLER32:02f80100"
@@ -180,7 +166,6 @@ Feature: upload resources on share using TUS protocol
       | Tus-Resumable   | 1.0.0                     |
     And user "Alice" has uploaded file with checksum "SHA1 8cb2237d0679ca88db6464eac60da96345513964" to the last created TUS Location with offset "0" and content "12345" via TUS inside of the space "Personal" using the WebDAV API
     And user "Alice" has shared file "/textFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/textFile.txt" offered by user "Alice"
     When user "Brian" downloads the file "/textFile.txt" of the space "Shares" using the WebDAV API
     Then the header checksum should match "SHA1:8cb2237d0679ca88db6464eac60da96345513964"
 
@@ -188,7 +173,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: sharee uploads a file to a received share folder with correct checksum
     Given user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" creates a new TUS resource for the space "Shares" with content "" using the WebDAV API with these headers:
       | Upload-Length   | 16                                    |
       #    L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt
@@ -203,7 +187,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: sharee uploads a file to a received share folder with wrong checksum should not work
     Given user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" creates a new TUS resource for the space "Shares" with content "" using the WebDAV API with these headers:
       | Upload-Length   | 16                                    |
       #    L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt
@@ -218,7 +201,6 @@ Feature: upload resources on share using TUS protocol
   Scenario: sharer uploads a file to shared folder with wrong checksum should not work
     Given user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Alice" has created a new TUS resource for the space "Personal" with content "" using the WebDAV API with these headers:
       | Upload-Length   | 16                                    |
       #    L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt
@@ -241,14 +223,14 @@ Feature: upload resources on share using TUS protocol
     When user "Alice" sends a chunk to the last created TUS Location with offset "0" and data "01234" with checksum "MD5 4100c4d44da9177247e44a5fc1546778" via TUS inside of the space "Personal" using the WebDAV API
     And user "Alice" sends a chunk to the last created TUS Location with offset "5" and data "56789" with checksum "MD5 099ebea48ea9666a7da2177267983138" via TUS inside of the space "Personal" using the WebDAV API
     And user "Alice" shares file "textFile.txt" with user "Brian" using the sharing API
-    And user "Brian" accepts share "/textFile.txt" offered by user "Alice" using the sharing API
-    Then for user "Brian" the content of the file "/textFile.txt" of the space "Shares" should be "0123456789"
+    Then the HTTP status code should be "200"
+    And the OCS status code should be "100"
+    And for user "Brian" the content of the file "/textFile.txt" of the space "Shares" should be "0123456789"
 
 
   Scenario: sharee uploads a chunked file with correct checksum to a received share folder should work
     Given user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Brian" has created a new TUS resource for the space "Shares" with content "" using the WebDAV API with these headers:
       | Upload-Length   | 10                                    |
       #    L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt
@@ -270,7 +252,6 @@ Feature: upload resources on share using TUS protocol
       | Tus-Resumable   | 1.0.0                     |
     And user "Alice" has uploaded file with checksum "SHA1 c1dab0c0864b6ac9bdd3743a1408d679f1acd823" to the last created TUS Location with offset "0" and content "original content" via TUS inside of the space "Personal" using the WebDAV API
     And user "Alice" has shared file "/textFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/textFile.txt" offered by user "Alice"
     When user "Brian" overwrites recently shared file with offset "0" and data "overwritten content" with checksum "SHA1 fe990d2686a0fc86004efc31f5bf2475a45d4905" via TUS inside of the space "Shares" using the WebDAV API with these headers:
       | Upload-Length   | 19                        |
       #    dGV4dEZpbGUudHh0 is the base64 encode of textFile.txt
@@ -288,7 +269,6 @@ Feature: upload resources on share using TUS protocol
       | Tus-Resumable   | 1.0.0                     |
     And user "Alice" has uploaded file with checksum "SHA1 c1dab0c0864b6ac9bdd3743a1408d679f1acd823" to the last created TUS Location with offset "0" and content "original content" via TUS inside of the space "Personal" using the WebDAV API
     And user "Alice" has shared file "/textFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/textFile.txt" offered by user "Alice"
     When user "Brian" overwrites recently shared file with offset "0" and data "overwritten content" with checksum "SHA1 fe990d2686a0fc86004efc31f5bf2475a45d4906" via TUS inside of the space "Shares" using the WebDAV API with these headers:
       | Upload-Length   | 19                        |
       #    dGV4dEZpbGUudHh0 is the base64 encode of textFile.txt

tests/acceptance/features/bootstrap/OcisConfigContext.php

@@ -86,8 +86,7 @@ class OcisConfigContext implements Context {
 	 * @throws GuzzleException
 	 */
 	public function theConfigHasBeenSetPathTo(string $configVariable, string $path): void {
-		$path = UploadHelper::getUploadFilesDir($path);
-	
+		$path = \dirname(__FILE__) . "/../../../" . $path;
 		$this->theConfigHasBeenSetTo($configVariable, $path);
 	}
 

tests/acceptance/features/bootstrap/SettingsContext.php

@@ -418,4 +418,56 @@ class SettingsContext implements Context {
 			$response
 		);
 	}
+
+	/**
+	 * @param string $user
+	 *
+	 * @return ResponseInterface
+	 *
+	 * @throws GuzzleException
+	 * @throws Exception
+	 */
+	public function sendRequestToDisableAutoAccepting(string $user): ResponseInterface {
+		$fullUrl = $this->baseUrl . $this->settingsUrl . "values-save";
+		$body = json_encode(
+			[
+			"value" => [
+			"account_uuid" => "me",
+			"bundleId" => "2a506de7-99bd-4f0d-994e-c38e72c28fd9",
+			"settingId" => "ec3ed4a3-3946-4efc-8f9f-76d38b12d3a9",
+			"resource" => [
+			"type" => "TYPE_USER"
+			],
+			"boolValue" => false
+			]
+			],
+			JSON_THROW_ON_ERROR
+		);
+		return $this->spacesContext->sendPostRequestToUrl(
+			$fullUrl,
+			$user,
+			$this->featureContext->getPasswordForUser($user),
+			$body,
+			$this->featureContext->getStepLineRef()
+		);
+	}
+
+	/**
+	 * @Given user :user has disabled auto-accepting
+	 *
+	 * @param string $user
+	 *
+	 * @return void
+	 *
+	 * @throws Exception
+	 * @throws GuzzleException
+	 */
+	public function theUserHasDisabledAutoAccepting(string $user): void {
+		$response = $this->sendRequestToDisableAutoAccepting($user);
+		$this->featureContext->theHTTPStatusCodeShouldBe(
+			201,
+			"Expected response status code should be 201",
+			$response
+		);
+	}
 }

tests/acceptance/features/coreApiFavorites/favoritesSharingToShares.feature

@@ -13,7 +13,6 @@ Feature: favorite
     Given using <dav-path-version> DAV path
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has shared folder "/PARENT" with user "Brian"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" favorites element "/Shares/PARENT/parent.txt" using the WebDAV API
     Then the HTTP status code should be "207"
     And as user "Brian" file "/Shares/PARENT/parent.txt" should be favorited
@@ -28,7 +27,6 @@ Feature: favorite
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/PARENT/sub-folder"
     And user "Alice" has shared folder "/PARENT" with user "Brian"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" favorites element "/Shares/PARENT/sub-folder" using the WebDAV API
     Then the HTTP status code should be "207"
     And as user "Brian" folder "/Shares/PARENT/sub-folder" should be favorited
@@ -42,7 +40,6 @@ Feature: favorite
     Given using <dav-path-version> DAV path
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has shared folder "/PARENT" with user "Brian"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" favorites element "/Shares/PARENT" using the WebDAV API
     Then the HTTP status code should be "207"
     And as user "Brian" folder "/Shares/PARENT" should be favorited
@@ -56,7 +53,6 @@ Feature: favorite
     Given using <dav-path-version> DAV path
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has shared folder "/PARENT" with user "Brian"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     And user "Brian" has favorited element "/Shares/PARENT/parent.txt"
     When user "Brian" moves file "/Shares/PARENT/parent.txt" to "/taken_out.txt" using the WebDAV API
     Then the HTTP status code should be "201"
@@ -72,7 +68,6 @@ Feature: favorite
     Given using <dav-path-version> DAV path
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has shared file "/PARENT/parent.txt" with user "Brian"
-    And user "Brian" has accepted share "/parent.txt" offered by user "Alice"
     When user "Brian" favorites element "/Shares/parent.txt" using the WebDAV API
     Then the HTTP status code should be "207"
     And as user "Brian" file "/Shares/parent.txt" should be favorited

tests/acceptance/features/coreApiMain/checksums.feature

@@ -180,7 +180,6 @@ Feature: checksums
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
     And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/myChecksumFile.txt" offered by user "Alice"
     When user "Brian" requests the checksum of "/Shares/myChecksumFile.txt" via propfind
     Then the HTTP status code should be "207"
     And the webdav checksum should match "SHA1:3ee962b839762adb0ad8ba6023a4690be478de6f MD5:d70b40f177b14b470d1756a3c12b963a ADLER32:8ae90960"
@@ -191,7 +190,6 @@ Feature: checksums
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
     And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/myChecksumFile.txt" offered by user "Alice"
     When user "Brian" uploads file with checksum "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399" and content "Some Text" to "/Shares/myChecksumFile.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And as user "Alice" the webdav checksum of "/myChecksumFile.txt" via propfind should match "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a"

tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareResourceCaseSensitiveName.feature

@@ -8,6 +8,7 @@ Feature: Sharing resources with different case names with the sharee and checkin
       | username |
       | Alice    |
       | Brian    |
+    And user "Brian" has disabled auto-accepting 
 
 
   Scenario: sharing files with different case names with an internal user

tests/acceptance/features/coreApiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature

@@ -16,9 +16,21 @@ Feature: resources shared with the same name are received with unique names
     Given user "Alice" has created folder "/foo"
     And user "Brian" has created folder "/foo"
     When user "Alice" shares folder "/foo" with user "Carol" using the sharing API
-    And user "Carol" accepts share "/foo" offered by user "Alice" using the sharing API
     And user "Brian" shares folder "/foo" with user "Carol" using the sharing API
-    And user "Carol" accepts share "/foo" offered by user "Brian" using the sharing API
+    Then the OCS status code of responses on all endpoints should be "100"
+    And the HTTP status code of responses on all endpoints should be "200"
+    And user "Carol" should see the following elements
+      | Shares/foo/      |
+      | /Shares/foo (1)/ |
+
+
+  @smokeTest @issue-2131
+  Scenario: unique target names for incoming shares when auto-accepting is disabled
+    Given user "Brian" has disabled auto-accepting
+    And user "Alice" has created folder "/foo"
+    And user "Brian" has created folder "/foo"
+    When user "Alice" shares folder "/foo" with user "Carol" using the sharing API
+    And user "Brian" shares folder "/foo" with user "Carol" using the sharing API
     Then the OCS status code of responses on all endpoints should be "100"
     And the HTTP status code of responses on all endpoints should be "200"
     And user "Carol" should see the following elements

tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature

@@ -13,7 +13,6 @@ Feature: shares are received in the default folder for received shares
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "FOLDER"
     When user "Alice" shares folder "/FOLDER" with user "Brian" using the sharing API
-    And user "Brian" accepts share "/FOLDER" offered by user "Alice" using the sharing API
     And user "Brian" declines share "/Shares/FOLDER" offered by user "Alice" using the sharing API
     And user "Brian" shares folder "/Shares" with user "Alice" using the sharing API
     Then the OCS status code of responses on each endpoint should be "<ocs_status_code>" respectively

tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareGroupAndUserWithSameName.feature

@@ -16,11 +16,9 @@ Feature: sharing works when a username and group name are the same
     And user "Carol" has been added to group "Brian"
     And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
     And user "Alice" has shared file "randomfile.txt" with group "Brian"
-    And user "Carol" has accepted share "/randomfile.txt" offered by user "Alice"
     When user "Alice" shares file "randomfile.txt" with user "Brian" using the sharing API
-    And user "Brian" accepts share "/randomfile.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "100"
-    And the HTTP status code of responses on all endpoints should be "200"
+    Then the HTTP status code should be "200"
+    And the OCS status code should be "100"
     And user "Brian" should see the following elements
       | /Shares/randomfile.txt |
     And user "Carol" should see the following elements
@@ -38,11 +36,9 @@ Feature: sharing works when a username and group name are the same
     And user "Carol" has been added to group "Brian"
     And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
     And user "Alice" has shared file "randomfile.txt" with user "Brian"
-    And user "Brian" has accepted share "/randomfile.txt" offered by user "Alice"
     When user "Alice" shares file "randomfile.txt" with group "Brian" using the sharing API
-    And user "Carol" accepts share "/randomfile.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "100"
-    And the HTTP status code of responses on all endpoints should be "200"
+    Then the HTTP status code should be "200"
+    And the OCS status code should be "100"
     And user "Brian" should see the following elements
       | /Shares/randomfile.txt |
     And user "Carol" should see the following elements
@@ -60,11 +56,9 @@ Feature: sharing works when a username and group name are the same
     And user "Carol" has been added to group "brian"
     And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
     And user "Alice" has shared file "randomfile.txt" with group "brian"
-    And user "Carol" has accepted share "/randomfile.txt" offered by user "Alice"
     When user "Alice" shares file "randomfile.txt" with user "Brian" using the sharing API
-    And user "Brian" accepts share "/randomfile.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "100"
-    And the HTTP status code of responses on all endpoints should be "200"
+    Then the HTTP status code should be "200"
+    And the OCS status code should be "100"
     And user "Brian" should see the following elements
       | /Shares/randomfile.txt |
     And user "Carol" should see the following elements
@@ -82,11 +76,9 @@ Feature: sharing works when a username and group name are the same
     And user "Carol" has been added to group "brian"
     And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
     And user "Alice" has shared file "randomfile.txt" with user "Brian"
-    And user "Brian" has accepted share "/randomfile.txt" offered by user "Alice"
     When user "Alice" shares file "randomfile.txt" with group "brian" using the sharing API
-    And user "Carol" accepts share "/randomfile.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "100"
-    And the HTTP status code of responses on all endpoints should be "200"
+    Then the HTTP status code should be "200"
+    And the OCS status code should be "100"
     And user "Carol" should see the following elements
       | /Shares/randomfile.txt |
     And user "Brian" should see the following elements

tests/acceptance/features/coreApiShareCreateSpecialToShares2/createShareReceivedInMultipleWays.feature

@@ -12,11 +12,11 @@ Feature: share resources where the sharee receives the share in multiple ways
 
   Scenario Outline: creating and accepting a new share with user who already received a share through their group
     Given using OCS API version "<ocs_api_version>"
+    And user "Brian" has disabled auto-accepting
     And group "grp1" has been created
     And user "Brian" has been added to group "grp1"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with group "grp1"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Alice" shares file "/textfile0.txt" with user "Brian" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -51,8 +51,6 @@ Feature: share resources where the sharee receives the share in multiple ways
     And user "Alice" shares folder "/PARENT/CHILD" with group "grp4" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Brian" should be able to accept pending share "/PARENT" offered by user "Alice"
-    And user "Brian" should be able to accept pending share "/CHILD" offered by user "Alice"
     And user "Brian" should see the following elements
       | /Shares/PARENT/           |
       | /Shares/PARENT/parent.txt |
@@ -73,7 +71,6 @@ Feature: share resources where the sharee receives the share in multiple ways
     When user "Alice" shares folder "/test/sub" with user "Brian" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Brian" should be able to accept pending share "/sub" offered by user "Alice"
     And as "Brian" folder "/Shares/sub" should exist
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -91,7 +88,6 @@ Feature: share resources where the sharee receives the share in multiple ways
     When user "Alice" shares folder "/test/sub" with user "Brian" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Brian" should be able to accept pending share "/sub" offered by user "Alice"
     And as "Brian" folder "/Shares/sub" should exist
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -105,7 +101,8 @@ Feature: share resources where the sharee receives the share in multiple ways
     And user "Brian" has uploaded file with content "First data" to "/randomfile.txt"
     And user "Carol" has uploaded file with content "Second data" to "/randomfile.txt"
     When user "Brian" shares file "randomfile.txt" with user "Alice" with permissions "read" using the sharing API
-    And user "Alice" accepts share "/randomfile.txt" offered by user "Brian" using the sharing API
+    Then the HTTP status code should be "200"
+    And the OCS status code should be "<ocs_status_code>"
     Then as "Alice" the info about the last share by user "Brian" with user "Alice" should include
       | uid_owner   | %username%      |
       | share_with  | %username%      |
@@ -113,8 +110,9 @@ Feature: share resources where the sharee receives the share in multiple ways
       | item_type   | file            |
       | permissions | read            |
     When user "Carol" shares file "randomfile.txt" with user "Alice" with permissions "read,update" using the sharing API
-    And user "Alice" accepts share "/randomfile.txt" offered by user "Carol" using the sharing API
-    Then as "Alice" the info about the last share by user "Carol" with user "Alice" should include
+    Then the HTTP status code should be "200"
+    And the OCS status code should be "<ocs_status_code>"
+    And as "Alice" the info about the last share by user "Carol" with user "Alice" should include
       | uid_owner   | %username%          |
       | share_with  | %username%          |
       | file_target | /randomfile (2).txt |
@@ -123,9 +121,9 @@ Feature: share resources where the sharee receives the share in multiple ways
     And the content of file "/Shares/randomfile.txt" for user "Alice" should be "First data"
     And the content of file "/Shares/randomfile (2).txt" for user "Alice" should be "Second data"
     Examples:
-      | ocs_api_version |
-      | 1               |
-      | 2               |
+      | ocs_api_version | ocs_status_code |
+      | 1               | 100             |
+      | 2               | 200             |
 
   @issue-2131
   Scenario Outline: multiple users share a folder with the same name to a user
@@ -136,7 +134,8 @@ Feature: share resources where the sharee receives the share in multiple ways
     And user "Carol" has created folder "/zzzfolder"
     And user "Carol" has created folder "zzzfolder/Carol"
     When user "Brian" shares folder "zzzfolder" with user "Alice" with permissions "read,delete" using the sharing API
-    And user "Alice" accepts share "/zzzfolder" offered by user "Brian" using the sharing API
+    Then the HTTP status code should be "200"
+    And the OCS status code should be "100"
     Then as "Alice" the info about the last share by user "Brian" with user "Alice" should include
       | uid_owner   | %username%  |
       | share_with  | %username%  |
@@ -146,7 +145,6 @@ Feature: share resources where the sharee receives the share in multiple ways
     When user "Carol" shares folder "zzzfolder" with user "Alice" with permissions "read,share" using the sharing API
     Then the HTTP status code should be "200"
     And the OCS status code should be "<ocs_status_code>"
-    And user "Alice" should be able to accept pending share "/zzzfolder" offered by user "Carol"
     And as "Alice" the info about the last share by user "Carol" with user "Alice" should include
       | uid_owner   | %username%     |
       | share_with  | %username%     |
@@ -174,7 +172,6 @@ Feature: share resources where the sharee receives the share in multiple ways
       | path      | /lorem.txt |
       | shareType | group      |
       | shareWith | grp1       |
-    And user "Brian" has accepted share "/lorem.txt" offered by user "Alice"
     When the administrator adds user "Carol" to group "grp1" using the provisioning API
     Then the HTTP status code should be "204"
     And user "Carol" should be able to accept pending share "/lorem.txt" offered by user "Alice"
@@ -207,11 +204,6 @@ Feature: share resources where the sharee receives the share in multiple ways
       | shareType   | group          |
       | shareWith   | grp1           |
       | permissions | read           |
-    When user "Brian" accepts share "/parent" offered by user "Carol" using the sharing API
-    And user "Brian" accepts share "/child1" offered by user "Carol" using the sharing API
-    And user "Alice" accepts share "/child1" offered by user "Carol" using the sharing API
-    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"
     And user "Brian" should be able to create folder "/Shares/parent/fo1"
     And user "Brian" should be able to create folder "/Shares/parent/child1/fo2"
     And user "Alice" should not be able to create folder "/Shares/child1/fo3"
@@ -238,11 +230,6 @@ Feature: share resources where the sharee receives the share in multiple ways
       | shareType   | group          |
       | shareWith   | grp1           |
       | permissions | read           |
-    When user "Brian" accepts share "/parent" offered by user "Carol" using the sharing API
-    And user "Brian" accepts share "/child1" offered by user "Carol" using the sharing API
-    And user "Alice" accepts share "/child1" offered by user "Carol" using the sharing API
-    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"
     And user "Brian" should be able to rename file "/Shares/parent/child1/child2/textfile-2.txt" to "/Shares/parent/child1/child2/rename.txt"
     And user "Brian" should not be able to rename file "/Shares/child1/child2/rename.txt" to "/Shares/child1/child2/rename2.txt"
     And user "Alice" should not be able to rename file "/Shares/child1/child2/rename.txt" to "/Shares/child1/child2/rename2.txt"
@@ -269,50 +256,41 @@ Feature: share resources where the sharee receives the share in multiple ways
       | shareType   | group          |
       | shareWith   | grp1           |
       | permissions | read           |
-    When user "Brian" accepts share "/parent" offered by user "Carol" using the sharing API
-    And user "Brian" accepts share "/child1" offered by user "Carol" using the sharing API
-    And user "Alice" accepts share "/child1" offered by user "Carol" using the sharing API
-    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"
     And user "Brian" should be able to delete file "/Shares/parent/child1/child2/textfile-2.txt"
     And user "Brian" should not be able to delete folder "/Shares/child1/child2"
     And user "Alice" should not be able to delete folder "/Shares/child1/child2"
 
 
-  Scenario: sharing parent folder to user with all permissions and its child folder to group with read permission then check reshare operation
-    Given group "grp1" has been created
-    And user "Carol" has been created with default attributes and without skeleton files
-    And user "Carol" has created the following folders
-      | path                  |
-      | /parent               |
-      | /parent/child1        |
-      | /parent/child1/child2 |
-    And user "Alice" has been added to group "grp1"
-    And user "Brian" has been added to group "grp1"
-    And user "Carol" has created a share with settings
-      | path        | /parent |
-      | shareType   | user    |
-      | shareWith   | Brian   |
-      | permissions | all     |
-    And user "Carol" has created a share with settings
-      | path        | /parent/child1 |
-      | shareType   | group          |
-      | shareWith   | grp1           |
-      | permissions | read           |
-    And user "Brian" has accepted share "/parent" offered by user "Carol"
-    And user "Brian" has accepted share "/child1" offered by user "Carol"
-    And user "Alice" has accepted share "/child1" offered by user "Carol"
-    When user "Brian" creates a share using the sharing API with settings
-      | path        | /Shares/parent |
-      | shareType   | user           |
-      | shareWith   | Alice          |
-      | permissions | read           |
-    Then the HTTP status code should be "200"
-    And the OCS status code should be "100"
-    And user "Alice" should be able to accept pending share "/parent" offered by user "Brian"
-    And as "Brian" folder "/Shares/child1" should exist
-    And as "Alice" folder "/Shares/child1" should exist
-    And as "Alice" folder "/Shares/parent" should exist
+  # Scenario: sharing parent folder to user with all permissions and its child folder to group with read permission then check reshare operation
+  #   Given group "grp1" has been created
+  #   And user "Carol" has been created with default attributes and without skeleton files
+  #   And user "Carol" has created the following folders
+  #     | path                  |
+  #     | /parent               |
+  #     | /parent/child1        |
+  #     | /parent/child1/child2 |
+  #   And user "Alice" has been added to group "grp1"
+  #   And user "Brian" has been added to group "grp1"
+  #   And user "Carol" has created a share with settings
+  #     | path        | /parent |
+  #     | shareType   | user    |
+  #     | shareWith   | Brian   |
+  #     | permissions | all     |
+  #   And user "Carol" has created a share with settings
+  #     | path        | /parent/child1 |
+  #     | shareType   | group          |
+  #     | shareWith   | grp1           |
+  #     | permissions | read           |
+  #   When user "Brian" creates a share using the sharing API with settings
+  #     | path        | /Shares/parent |
+  #     | shareType   | user           |
+  #     | shareWith   | Alice          |
+  #     | permissions | read           |
+  #   Then the HTTP status code should be "200"
+  #   And the OCS status code should be "100"
+  #   And as "Brian" folder "/Shares/child1" should exist
+  #   And as "Alice" folder "/Shares/child1" should exist
+  #   And as "Alice" folder "/Shares/parent" should exist
 
 
   Scenario: sharing parent folder to group with read permission and its child folder to user with all permissions then check create operation
@@ -335,11 +313,6 @@ Feature: share resources where the sharee receives the share in multiple ways
       | shareType   | user           |
       | shareWith   | Brian          |
       | permissions | all            |
-    When user "Brian" accepts share "/child1" offered by user "Carol" using the sharing API
-    And user "Brian" accepts share "/parent" offered by user "Carol" using the sharing API
-    And user "Alice" accepts share "/parent" offered by user "Carol" using the sharing API
-    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"
     And user "Brian" should be able to create folder "/Shares/child1/fo1"
     And user "Brian" should be able to create folder "/Shares/child1/child2/fo2"
     But user "Brian" should not be able to create folder "/Shares/parent/fo3"
@@ -368,11 +341,6 @@ Feature: share resources where the sharee receives the share in multiple ways
       | shareType   | user           |
       | shareWith   | Brian          |
       | permissions | all            |
-    When user "Brian" accepts share "/child1" offered by user "Carol" using the sharing API
-    And user "Brian" accepts share "/parent" offered by user "Carol" using the sharing API
-    And user "Alice" accepts share "/parent" offered by user "Carol" using the sharing API
-    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"
     And user "Brian" should be able to rename file "/Shares/child1/child2/textfile-2.txt" to "/Shares/child1/child2/rename.txt"
     And user "Brian" should not be able to rename file "/Shares/parent/child1/child2/rename.txt" to "/Shares/parent/child1/child2/rename2.txt"
     And user "Alice" should not be able to rename file "/Shares/parent/child1/child2/rename.txt" to "/Shares/parent/child1/child2/rename2.txt"
@@ -399,11 +367,6 @@ Feature: share resources where the sharee receives the share in multiple ways
       | shareType   | user           |
       | shareWith   | Brian          |
       | permissions | all            |
-    When user "Brian" accepts share "/child1" offered by user "Carol" using the sharing API
-    And user "Brian" accepts share "/parent" offered by user "Carol" using the sharing API
-    And user "Alice" accepts share "/parent" offered by user "Carol" using the sharing API
-    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"
     And user "Brian" should be able to delete file "/Shares/child1/child2/textfile-2.txt"
     And user "Brian" should not be able to delete folder "/Shares/parent/child1"
     And user "Alice" should not be able to delete folder "/Shares/parent/child1"
@@ -429,13 +392,7 @@ Feature: share resources where the sharee receives the share in multiple ways
       | shareType   | user           |
       | shareWith   | Brian          |
       | permissions | all            |
-    When user "Brian" accepts share "/child1" offered by user "Carol" using the sharing API
-    And user "Brian" accepts share "/parent" offered by user "Carol" using the sharing API
-    And user "Alice" accepts share "/parent" offered by user "Carol" using the sharing API
-    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"
     And user "Brian" should be able to share folder "/Shares/child1" with user "Alice" with permissions "read" using the sharing API
-    And user "Alice" should be able to accept pending share "/child1" offered by user "Brian"
     And as "Brian" folder "/Shares/parent" should exist
     And as "Alice" folder "/Shares/parent" should exist
     And as "Alice" folder "/Shares/child1" should exist
@@ -466,10 +423,6 @@ Feature: share resources where the sharee receives the share in multiple ways
       | shareType   | group          |
       | shareWith   | grp2           |
       | permissions | read           |
-    When user "Alice" accepts share "/parent" offered by user "Carol" using the sharing API
-    And user "Brian" accepts share "/child1" offered by user "Carol" using the sharing API
-    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"
     And user "Alice" should be able to create folder "/Shares/parent/child1/fo1"
     And user "Alice" should be able to create folder "/Shares/parent/child1/child2/fo2"
     And user "Alice" should be able to delete folder "/Shares/parent/child1/fo1"
@@ -483,9 +436,8 @@ Feature: share resources where the sharee receives the share in multiple ways
     And user "Brian" should not be able to share folder "/Shares/child1" with group "grp3" with permissions "read" using the sharing API
 
 
-  Scenario Outline: share receiver renames the received group share and shares same folder through user share again
-    Given using OCS API version "<ocs_api_version>"
-    And group "grp" has been created
+  Scenario: share receiver renames the received group share and shares same folder through user share again
+    Given group "grp" has been created
     And user "Brian" has been added to group "grp"
     And user "Alice" has been added to group "grp"
     And user "Alice" has created folder "parent"
@@ -496,9 +448,6 @@ Feature: share resources where the sharee receives the share in multiple ways
       | shareType   | group  |
       | shareWith   | grp    |
       | permissions | read   |
-    When user "Brian" accepts share "/parent" offered by user "Alice" using the sharing API
-    Then the HTTP status code should be "200"
-    And the OCS status code should be "<ocs_status_code>"
     And user "Brian" should be able to rename folder "/Shares/parent" to "/Shares/sharedParent"
     And user "Alice" should be able to share folder "parent" with user "Brian" with permissions "read" using the sharing API
     # Note: Brian has already accepted the share of this resource as a member of "grp".
@@ -508,53 +457,44 @@ Feature: share resources where the sharee receives the share in multiple ways
     And as "Brian" folder "Shares/parent" should not exist
     And as "Brian" folder "Shares/sharedParent" should exist
     And as "Brian" file "Shares/sharedParent/child/lorem.txt" should exist
-    Examples:
-      | ocs_api_version | ocs_status_code |
-      | 1               | 100             |
-      | 2               | 200             |
 
 
-  Scenario Outline: share receiver renames a group share and receives same resource through user share with additional permissions
-    Given using OCS API version "<ocs_api_version>"
-    And group "grp" has been created
-    And user "Brian" has been added to group "grp"
-    And user "Alice" has been added to group "grp"
-    And user "Alice" has created folder "parent"
-    And user "Alice" has created folder "parent/child"
-    And user "Alice" has uploaded file with content "Share content" to "parent/child/lorem.txt"
-    And user "Alice" has created a share with settings
-      | path        | parent |
-      | shareType   | group  |
-      | shareWith   | grp    |
-      | permissions | read   |
-    And user "Brian" has accepted share "/parent" offered by user "Alice"
-    And user "Brian" has moved folder "/Shares/parent" to "/Shares/sharedParent"
-    When user "Alice" shares folder "parent" with user "Brian" with permissions "all" using the sharing API
-    # Note: Brian has already accepted the share of this resource as a member of "grp".
-    #       Now he has also received the same resource shared directly to "Brian".
-    #       The server should effectively "auto-accept" this new "copy" of the resource
-    #       and present to Brian only the single resource "Shares/sharedParent"
-    Then as "Brian" folder "Shares/parent" should not exist
-    And as "Brian" folder "Shares/sharedParent" should exist
-    And as "Brian" file "Shares/sharedParent/child/lorem.txt" should exist
-    Examples:
-      | ocs_api_version |
-      | 1               |
-      | 2               |
+  # Scenario Outline: share receiver renames a group share and receives same resource through user share with additional permissions
+  #   Given using OCS API version "<ocs_api_version>"
+  #   And group "grp" has been created
+  #   And user "Brian" has been added to group "grp"
+  #   And user "Alice" has been added to group "grp"
+  #   And user "Alice" has created folder "parent"
+  #   And user "Alice" has created folder "parent/child"
+  #   And user "Alice" has uploaded file with content "Share content" to "parent/child/lorem.txt"
+  #   And user "Alice" has created a share with settings
+  #     | path        | parent |
+  #     | shareType   | group  |
+  #     | shareWith   | grp    |
+  #     | permissions | read   |
+  #   And user "Brian" has moved folder "/Shares/parent" to "/Shares/sharedParent"
+  #   When user "Alice" shares folder "parent" with user "Brian" with permissions "all" using the sharing API
+  #   # Note: Brian has already accepted the share of this resource as a member of "grp".
+  #   #       Now he has also received the same resource shared directly to "Brian".
+  #   #       The server should effectively "auto-accept" this new "copy" of the resource
+  #   #       and present to Brian only the single resource "Shares/sharedParent"
+  #   Then as "Brian" folder "Shares/parent" should not exist
+  #   And as "Brian" folder "Shares/sharedParent" should exist
+  #   And as "Brian" file "Shares/sharedParent/child/lorem.txt" should exist
+  #   Examples:
+  #     | ocs_api_version |
+  #     | 1               |
+  #     | 2               |
 
 
-  Scenario Outline: share receiver renames a group share and receives same resource through user share with less permissions
-    Given using OCS API version "<ocs_api_version>"
-    And group "grp" has been created
+  Scenario: share receiver renames a group share and receives same resource through user share with less permissions
+    Given group "grp" has been created
     And user "Brian" has been added to group "grp"
     And user "Alice" has been added to group "grp"
     And user "Alice" has created folder "parent"
     And user "Alice" has created folder "parent/child"
     And user "Alice" has uploaded file with content "Share content" to "parent/child/lorem.txt"
     And user "Alice" has shared folder "parent" with group "grp" with permissions "all"
-    When user "Brian" accepts share "/parent" offered by user "Alice" using the sharing API
-    Then the HTTP status code should be "200"
-    And the OCS status code should be "<ocs_status_code>"
     And user "Brian" should be able to rename folder "/Shares/parent" to "/Shares/sharedParent"
     And user "Alice" should be able to share folder "parent" with user "Brian" with permissions "read" using the sharing API
     # Note: Brian has already accepted the share of this resource as a member of "grp".
@@ -564,7 +504,3 @@ Feature: share resources where the sharee receives the share in multiple ways
     And as "Brian" folder "Shares/parent" should not exist
     And as "Brian" folder "Shares/sharedParent" should exist
     And as "Brian" file "Shares/sharedParent/child/lorem.txt" should exist
-    Examples:
-      | ocs_api_version | ocs_status_code |
-      | 1               | 100             |
-      | 2               | 200             |

tests/acceptance/features/coreApiShareManagementBasicToShares/createShareToSharesFolder.feature

@@ -27,9 +27,6 @@ Feature: sharing
       | mimetype               | text/plain            |
       | storage_id             | ANY_VALUE             |
       | share_type             | user                  |
-    When user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code should be "<ocs_status_code>"
-    And the HTTP status code should be "200"
     And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud test text file 0"
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -56,9 +53,6 @@ Feature: sharing
       | mimetype               | text/plain           |
       | storage_id             | ANY_VALUE            |
       | share_type             | user                 |
-    When user "Brian" accepts share "/sample,1.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code should be "<ocs_status_code>"
-    And the HTTP status code should be "200"
     And the content of file "/Shares/sample,1.txt" for user "Brian" should be "file with comma in filename"
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -208,9 +202,8 @@ Feature: sharing
       | 2               | 200             |
 
   @smokeTest
-  Scenario Outline: share of folder to a group
-    Given using OCS API version "<ocs_api_version>"
-    And these users have been created with default attributes and without skeleton files:
+  Scenario: share of folder to a group
+    Given these users have been created with default attributes and without skeleton files:
       | username |
       | Brian    |
       | Carol    |
@@ -220,42 +213,27 @@ Feature: sharing
     And user "Alice" has created folder "/PARENT"
     And user "Alice" has uploaded file with content "file in parent folder" to "/PARENT/parent.txt"
     When user "Alice" shares folder "/PARENT" with group "grp1" using the sharing API
-    And user "Brian" accepts share "/PARENT" offered by user "Alice" using the sharing API
-    And user "Carol" accepts share "/PARENT" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "<ocs_status_code>"
-    And the HTTP status code of responses on all endpoints should be "200"
     And user "Brian" should see the following elements
       | /Shares/PARENT/           |
       | /Shares/PARENT/parent.txt |
     And user "Carol" should see the following elements
       | /Shares/PARENT/           |
       | /Shares/PARENT/parent.txt |
-    Examples:
-      | ocs_api_version | ocs_status_code |
-      | 1               | 100             |
-      | 2               | 200             |
 
   @smokeTest @skipOnReva # reva doesn't have a pre-created admin user
-  Scenario Outline: user included in multiple groups receives a share from the admin
-    Given using OCS API version "<ocs_api_version>"
+  Scenario: user included in multiple groups receives a share from the admin
     And group "grp1" has been created
     And group "grp2" has been created
     And user "Alice" has been added to group "grp1"
     And user "Alice" has been added to group "grp2"
     And admin has created folder "/PARENT"
     When user "admin" shares folder "/PARENT" with group "grp1" using the sharing API
-    And user "Alice" accepts share "/PARENT" offered by user "admin" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "<ocs_status_code>"
-    And the HTTP status code of responses on all endpoints should be "200"
-    Examples:
-      | ocs_api_version | ocs_status_code |
-      | 1               | 100             |
-      | 2               | 200             |
+    Then user "Alice" should see the following elements
+      | /Shares/PARENT/ |
 
   @smokeTest
-  Scenario Outline: user included in multiple groups, shares a folder with a group
-    Given using OCS API version "<ocs_api_version>"
-    And these users have been created with default attributes and without skeleton files:
+  Scenario: user included in multiple groups, shares a folder with a group
+    Given these users have been created with default attributes and without skeleton files:
       | username |
       | Brian    |
     And group "grp1" has been created
@@ -265,19 +243,13 @@ Feature: sharing
     And user "Brian" has been added to group "grp1"
     And user "Brian" has been added to group "grp2"
     And user "Alice" has created folder "/PARENT"
-    When user "Alice" shares folder "/PARENT" with group "grp1" using the sharing API
-    And user "Brian" accepts share "/PARENT" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "<ocs_status_code>"
-    And the HTTP status code of responses on all endpoints should be "200"
-    Examples:
-      | ocs_api_version | ocs_status_code |
-      | 1               | 100             |
-      | 2               | 200             |
+    When user "Alice" shares folder "/PARENT" with group "grp1" using the sharing API 
+    Then user "Brian" should see the following elements
+      | /Shares/PARENT |
 
 
-  Scenario Outline: sharing again an own file while belonging to a group
-    Given using OCS API version "<ocs_api_version>"
-    And user "Brian" has been created with default attributes and without skeleton files
+  Scenario: sharing again an own file while belonging to a group
+    Given user "Brian" has been created with default attributes and without skeleton files
     And group "grp1" has been created
     And user "Alice" has been added to group "grp1"
     And user "Brian" has been added to group "grp1"
@@ -285,15 +257,8 @@ Feature: sharing
     And user "Brian" has shared file "randomfile.txt" with group "grp1"
     And user "Brian" has deleted the last share
     When user "Brian" shares file "/randomfile.txt" with group "grp1" using the sharing API
-    And user "Alice" accepts share "/randomfile.txt" offered by user "Brian" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "<ocs_status_code>"
-    And the HTTP status code of responses on all endpoints should be "200"
     And as "Alice" file "/Shares/randomfile.txt" should exist
-    Examples:
-      | ocs_api_version | ocs_status_code |
-      | 1               | 100             |
-      | 2               | 200             |
-
+  
   @issue-2201
   Scenario Outline: sharing subfolder of already shared folder, GET result is correct
     Given using OCS API version "<ocs_api_version>"
@@ -333,10 +298,7 @@ Feature: sharing
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     And user "Alice" has moved file "textfile0.txt" to "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt"
     When user "Alice" shares file "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" with user "Brian" using the sharing API
-    And user "Brian" accepts share "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "<ocs_status_code>"
-    And the HTTP status code of responses on all endpoints should be "200"
-    And as "Brian" file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" should exist
+    Then as "Brian" file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" should exist
     Examples:
       | ocs_api_version | ocs_status_code |
       | 1               | 100             |
@@ -351,10 +313,7 @@ Feature: sharing
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     And user "Alice" has moved file "textfile0.txt" to "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt"
     When user "Alice" shares file "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" with group "grp1" using the sharing API
-    And user "Brian" accepts share "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "<ocs_status_code>"
-    And the HTTP status code of responses on all endpoints should be "200"
-    And as "Brian" file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" should exist
+    Then as "Brian" file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog.txt" should exist
     Examples:
       | ocs_api_version | ocs_status_code |
       | 1               | 100             |
@@ -368,10 +327,7 @@ Feature: sharing
     And user "Alice" has created folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog"
     And user "Alice" has moved file "textfile0.txt" to "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt"
     When user "Alice" shares folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog" with user "Brian" using the sharing API
-    And user "Brian" accepts share "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "<ocs_status_code>"
-    And the HTTP status code of responses on all endpoints should be "200"
-    And the content of file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt" for user "Brian" should be "ownCloud test"
+    Then the content of file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt" for user "Brian" should be "ownCloud test"
     Examples:
       | ocs_api_version | ocs_status_code |
       | 1               | 100             |
@@ -387,10 +343,7 @@ Feature: sharing
     And user "Alice" has created folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog"
     And user "Alice" has moved file "textfile0.txt" to "aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt"
     When user "Alice" shares folder "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog" with group "grp1" using the sharing API
-    And user "Brian" accepts share "/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "<ocs_status_code>"
-    And the HTTP status code of responses on all endpoints should be "200"
-    And the content of file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt" for user "Brian" should be "ownCloud test"
+    Then the content of file "/Shares/aquickbrownfoxjumpsoveraverylazydogaquickbrownfoxjumpsoveralazydog/textfile0.txt" for user "Brian" should be "ownCloud test"
     Examples:
       | ocs_api_version | ocs_status_code |
       | 1               | 100             |
@@ -411,10 +364,7 @@ Feature: sharing
       | path        | /randomfile.txt        |
       | permissions | share,read,update      |
       | uid_owner   | %username%             |
-    When user "brian" accepts share "/randomfile.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code should be "100"
-    And the HTTP status code should be "200"
-    And user "brian" should see the following elements
+    Then user "brian" should see the following elements
       | /Shares/randomfile.txt |
     And the content of file "Shares/randomfile.txt" for user "brian" should be "Random data"
 
@@ -427,10 +377,7 @@ Feature: sharing
     And user "Brian" has been added to group "grp1"
     And user "Alice" has uploaded file with content "Random data" to "/randomfile.txt"
     And user "Alice" has shared file "randomfile.txt" with group "grp1"
-    When user "Brian" accepts share "/randomfile.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code should be "100"
-    And the HTTP status code should be "200"
-    And user "Brian" should see the following elements
+    Then user "Brian" should see the following elements
       | /Shares/randomfile.txt |
     And the content of file "/Shares/randomfile.txt" for user "Brian" should be "Random data"
 
@@ -449,13 +396,7 @@ Feature: sharing
     When user "Alice" shares folder "/PARENT" with group "😀 😁" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Brian" accepts share "/PARENT" offered by user "Alice" using the sharing API
-    And the OCS status code should be "<ocs_status_code>"
-    And the HTTP status code should be "200"
-    And user "Carol" accepts share "/PARENT" offered by user "Alice" using the sharing API
-    And the OCS status code should be "<ocs_status_code>"
-    And the HTTP status code should be "200"
-    And user "Brian" should see the following elements
+    Then user "Brian" should see the following elements
       | /Shares/PARENT/           |
       | /Shares/PARENT/parent.txt |
     And user "Carol" should see the following elements
@@ -479,11 +420,8 @@ Feature: sharing
     And user "Brian" has been added to group "grp1"
     And user "Alice" has uploaded file with content "some content" to "lorem.txt"
     When user "Alice" shares file "lorem.txt" with group "grp1" using the sharing API
-    And user "Brian" accepts share "/lorem.txt" offered by user "Alice" using the sharing API
-    And the administrator adds user "Carol" to group "grp1" using the provisioning API
-    And user "Carol" accepts share "/lorem.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "<ocs_status_code>"
-    And the HTTP status code of responses on all endpoints should be "200"
+    Then the OCS status code should be "<ocs_status_code>"
+    And the HTTP status code should be "200"
     And the content of file "/Shares/lorem.txt" for user "Brian" should be "some content"
     And the content of file "/Shares/lorem.txt" for user "Carol" should be "some content"
     Examples:
@@ -512,8 +450,6 @@ Feature: sharing
       | file_target | /textfile0.txt |
       | path        | /textfile0.txt |
       | uid_owner   | %username%     |
-    When user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
-    And user "Carol" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
     Then as "Brian" file "/Shares/textfile0.txt" should exist
     And as "Carol" file "/Shares/textfile0.txt" should exist
     When the administrator deletes group "grp1" using the provisioning API
@@ -540,11 +476,8 @@ Feature: sharing
     And user "Alice" has created folder "/common"
     And user "Alice" has created folder "/common/sub"
     And user "Alice" has shared folder "common" with group "grp1"
-    And user "Brian" has accepted share "/common" offered by user "Alice"
-    And user "Carol" has accepted share "/common" offered by user "Alice"
     And user "Brian" has uploaded file with content "ownCloud" to "/textfile0.txt"
     And user "Brian" has shared file "textfile0.txt" with user "Carol"
-    And user "Carol" has accepted share "/textfile0.txt" offered by user "Brian"
     And user "Brian" has moved file "/textfile0.txt" to "/Shares/common/textfile0.txt"
     And user "Brian" has moved file "/Shares/common/textfile0.txt" to "/Shares/common/sub/textfile0.txt"
     When user "Carol" uploads file "filesForUpload/file_to_overwrite.txt" to "/Shares/textfile0.txt" using the WebDAV API
@@ -565,10 +498,8 @@ Feature: sharing
       | Carol    |
     And user "Alice" has created folder "userZeroFolder"
     And user "Alice" has shared folder "userZeroFolder" with user "Brian"
-    And user "Brian" has accepted share "/userZeroFolder" offered by user "Alice"
     And user "Brian" has created folder "/Shares/userZeroFolder/userOneFolder"
     And user "Brian" has shared folder "/Shares/userZeroFolder/userOneFolder" with user "Carol" with permissions "read, share"
-    And user "Carol" has accepted share "/userOneFolder" offered by user "Brian"
     When user "Carol" shares folder "/Shares/userOneFolder" with user "Brian" using the sharing API
     Then the HTTP status code should be "200"
     #    Then the HTTP status code should be "405"
@@ -583,10 +514,8 @@ Feature: sharing
       | Carol    |
     And user "Alice" has created folder "userZeroFolder"
     And user "Alice" has shared folder "userZeroFolder" with user "Brian"
-    And user "Brian" has accepted share "/userZeroFolder" offered by user "Alice"
     And user "Brian" has created folder "/Shares/userZeroFolder/userOneFolder"
     And user "Brian" has shared folder "/Shares/userZeroFolder/userOneFolder" with user "Carol" with permissions "read, share"
-    And user "Carol" has accepted share "/userOneFolder" offered by user "Brian"
     When user "Carol" shares folder "/Shares/userOneFolder" with user "Alice" using the sharing API
     Then the HTTP status code should be "200"
     #    Then the HTTP status code should be "405"
@@ -603,11 +532,8 @@ Feature: sharing
     And user "Alice" has created folder "userZeroFolder"
     And user "Alice" has shared folder "userZeroFolder" with user "Brian"
     And user "Alice" has shared folder "userZeroFolder" with user "Carol"
-    And user "Brian" has accepted share "/userZeroFolder" offered by user "Alice"
-    And user "Carol" has accepted share "/userZeroFolder" offered by user "Alice"
     And user "Brian" has created folder "/Shares/userZeroFolder/userOneFolder"
     And user "Brian" has shared folder "/Shares/userZeroFolder/userOneFolder" with user "David" with permissions "read, share"
-    And user "David" has accepted share "/userOneFolder" offered by user "Brian"
     When user "David" shares folder "/Shares/userOneFolder" with user "Carol" using the sharing API
     Then the HTTP status code should be "200"
     #    Then the HTTP status code should be "405"
@@ -635,9 +561,6 @@ Feature: sharing
       | mimetype               | text/plain          |
       | storage_id             | ANY_VALUE           |
       | share_type             | user                |
-    When user "Brian" accepts share "/renamed.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code should be "<ocs_status_code>"
-    And the HTTP status code should be "200"
     And the content of file "/Shares/renamed.txt" for user "Brian" should be "ownCloud test text file 0"
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -654,8 +577,6 @@ Feature: sharing
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
     And user "Alice" has shared file "textfile0.txt" with user "Carol"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
-    And user "Carol" has accepted share "/textfile0.txt" offered by user "Alice"
     And the administrator has deleted user "Brian" using the provisioning API
     When user "Alice" gets all the shares of the file "textfile0.txt" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
@@ -674,7 +595,6 @@ Feature: sharing
     And user "Alice" has created folder "/Folder1"
     And user "Alice" has created folder "/Folder2"
     And user "Alice" has shared folder "/Folder1" with user "Brian"
-    And user "Brian" has accepted share "/Folder1" offered by user "Alice"
     And user "Alice" has moved file "/Folder2" to "/renamedFolder2"
     When user "Alice" shares folder "/renamedFolder2" with user "Brian" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
@@ -691,9 +611,6 @@ Feature: sharing
       | mimetype               | httpd/unix-directory   |
       | storage_id             | ANY_VALUE              |
       | share_type             | user                   |
-    When user "Brian" accepts share "/renamedFolder2" offered by user "Alice" using the sharing API
-    Then the OCS status code should be "<ocs_status_code>"
-    And the HTTP status code should be "200"
     And as "Brian" folder "/Shares/renamedFolder2" should exist
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -722,7 +639,6 @@ Feature: sharing
     And user "Carol" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" shares folder "Shares" with user "Carol" using the sharing API
     Then the HTTP status code should be "<http-status>"
     And the OCS status code should be "403"
@@ -741,7 +657,6 @@ Feature: sharing
     And user "Carol" has been added to group "share_group"
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" shares folder "Shares" with group "share_group" using the sharing API
     Then the HTTP status code should be "<http-status>"
     And the OCS status code should be "403"
@@ -757,7 +672,6 @@ Feature: sharing
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" creates a public link share of folder "Shares" using the sharing API
     Then the HTTP status code should be "<http-status>"
     And the OCS status code should be "403"

tests/acceptance/features/coreApiShareManagementBasicToShares/deleteShareFromShares.feature

@@ -17,7 +17,6 @@ Feature: sharing
     And group "grp1" has been created
     And user "Brian" has been added to group "grp1"
     And user "Alice" has shared file "textfile0.txt" with group "grp1"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Brian" has moved file "/Shares/textfile0.txt" to "/Shares/anotherName.txt"
     When user "Alice" deletes the last share using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
@@ -34,7 +33,6 @@ Feature: sharing
   Scenario Outline: delete a share
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Alice" deletes the last share using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -51,7 +49,6 @@ Feature: sharing
     And user "Alice" has created folder "/common"
     And user "Alice" has created folder "/common/sub"
     And user "Alice" has shared folder "/common/sub" with user "Brian"
-    And user "Brian" has accepted share "/sub" offered by user "Alice"
     When user "Alice" deletes folder "/common" using the WebDAV API
     Then the HTTP status code should be "204"
     And as "Brian" folder "/Shares/sub" should not exist
@@ -63,7 +60,6 @@ Feature: sharing
     And user "Alice" has created folder "/shared"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
     And user "Alice" has shared folder "/shared" with user "Brian"
-    And user "Brian" has accepted share "/shared" offered by user "Alice"
     When user "Brian" deletes file "/Shares/shared/shared_file.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And as "Brian" file "/Shares/shared/shared_file.txt" should not exist
@@ -78,7 +74,6 @@ Feature: sharing
     And user "Alice" has created folder "/shared/sub"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/sub/shared_file.txt"
     And user "Alice" has shared folder "/shared" with user "Brian"
-    And user "Brian" has accepted share "/shared" offered by user "Alice"
     When user "Brian" deletes folder "/Shares/shared/sub" using the WebDAV API
     Then the HTTP status code should be "204"
     And as "Brian" folder "/Shares/shared/sub" should not exist
@@ -99,7 +94,6 @@ Feature: sharing
     And user "Carol" has created folder "PARENT"
     And user "Carol" has uploaded file "filesForUpload/textfile.txt" to "PARENT/parent.txt"
     And user "Carol" has shared file "/PARENT/parent.txt" with group "grp1"
-    And user "Brian" has accepted share "/parent.txt" offered by user "Carol"
     And user "Carol" has stored etag of element "/PARENT"
     And user "Brian" has stored etag of element "/"
     And user "Brian" has stored etag of element "/Shares"
@@ -115,7 +109,6 @@ Feature: sharing
     And user "Alice" has created folder "/shared"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
     And user "Alice" has shared folder "shared" with user "Brian" with permissions "read"
-    And user "Brian" has accepted share "/shared" offered by user "Alice"
     When user "Brian" deletes file "/Shares/shared/shared_file.txt" using the WebDAV API
     Then the HTTP status code should be "403"
     And as "Alice" file "/shared/shared_file.txt" should exist
@@ -127,7 +120,6 @@ Feature: sharing
     And user "Alice" has created folder "/shared"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
     And user "Alice" has shared folder "shared" with user "Brian" with permissions "create"
-    And user "Brian" has accepted share "/shared" offered by user "Alice"
     When user "Brian" deletes file "/Shares/shared/shared_file.txt" using the WebDAV API
     Then the HTTP status code should be "403"
     And as "Alice" file "/shared/shared_file.txt" should exist
@@ -139,7 +131,6 @@ Feature: sharing
     Given using OCS API version "1"
     And user "Alice" has created folder "/shared"
     And user "Alice" has shared folder "shared" with user "Brian" with permissions "create"
-    And user "Brian" has accepted share "/shared" offered by user "Alice"
     And user "Brian" has uploaded file "filesForUpload/textfile.txt" to "/Shares/shared/textfile.txt"
     When user "Brian" deletes file "/Shares/shared/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "403"
@@ -159,8 +150,6 @@ Feature: sharing
     And user "Alice" has created folder "/shared"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
     And user "Alice" has shared entry "<entry_to_share>" with group "grp1"
-    And user "Brian" has accepted share "<pending_entry>" offered by user "Alice"
-    And user "Carol" has accepted share "<pending_entry>" offered by user "Alice"
     When user "Brian" deletes the last share of user "Alice" using the sharing API
     Then the OCS status code should be "404"
     And the HTTP status code should be "<http_status_code>"
@@ -180,7 +169,6 @@ Feature: sharing
     And user "Alice" has created folder "/shared"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
     And user "Alice" has shared entry "<entry_to_share>" with user "Brian"
-    And user "Brian" has accepted share "<pending_entry>" offered by user "Alice"
     When user "Brian" deletes the last share of user "Alice" using the sharing API
     Then the OCS status code should be "404"
     And the HTTP status code should be "<http_status_code>"
@@ -197,7 +185,6 @@ Feature: sharing
   Scenario Outline: request PROPFIND after sharer deletes the collaborator
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Alice" deletes the last share using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -212,7 +199,6 @@ Feature: sharing
   Scenario Outline: delete a share with wrong authentication
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" tries to delete the last share of user "Alice" using the sharing API
     Then the OCS status code should be "404"
     And the HTTP status code should be "<http_status_code>"
@@ -225,7 +211,6 @@ Feature: sharing
   Scenario Outline: unshare a shared resources
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Alice" unshares file "textfile0.txt" shared to "Brian"
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"

tests/acceptance/features/coreApiShareManagementToShares/acceptShares.feature

@@ -26,7 +26,9 @@ Feature: accept/decline shares coming from internal users
 
   @smokeTest  @issue-2540
   Scenario: share a file & folder with another internal group when auto accept is disabled
-    Given user "Carol" has created folder "FOLDER"
+    Given user "Brian" has disabled auto-accepting
+    And user "Carol" has disabled auto-accepting
+    And user "Carol" has created folder "FOLDER"
     And user "Carol" has created folder "PARENT"
     And user "Carol" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt"
     When user "Alice" shares folder "/PARENT" with group "grp1" using the sharing API
@@ -60,6 +62,7 @@ Feature: accept/decline shares coming from internal users
 
   @issue-2540
   Scenario: share a file & folder with another internal user when auto accept is disabled
+    Given user "Brian" has disabled auto-accepting
     When user "Alice" shares folder "/PARENT" with user "Brian" using the sharing API
     And user "Alice" shares file "/textfile0.txt" with user "Brian" using the sharing API
     Then the OCS status code of responses on all endpoints should be "100"
@@ -79,7 +82,8 @@ Feature: accept/decline shares coming from internal users
 
   @smokeTest @issue-2131
   Scenario: accept a pending share
-    Given user "Alice" has shared folder "/PARENT" with user "Brian"
+    Given user "Brian" has disabled auto-accepting
+    And user "Alice" has shared folder "/PARENT" with user "Brian"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian"
     When user "Brian" accepts share "/PARENT" offered by user "Alice" using the sharing API
     And user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
@@ -119,7 +123,8 @@ Feature: accept/decline shares coming from internal users
 
 
   Scenario: accept an accepted share
-    Given user "Alice" has created folder "/shared"
+    Given user "Brian" has disabled auto-accepting
+    And user "Alice" has created folder "/shared"
     And user "Alice" has shared folder "/shared" with user "Brian"
     When user "Brian" accepts share "/shared" offered by user "Alice" using the sharing API
     Then the OCS status code should be "100"
@@ -132,7 +137,8 @@ Feature: accept/decline shares coming from internal users
 
   @smokeTest  @issue-2540
   Scenario: declines a pending share
-    Given user "Alice" has shared folder "/PARENT" with user "Brian"
+    Given user "Brian" has disabled auto-accepting
+    And user "Alice" has shared folder "/PARENT" with user "Brian"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian"
     When user "Brian" declines share "/PARENT" offered by user "Alice" using the sharing API
     And user "Brian" declines share "/textfile0.txt" offered by user "Alice" using the sharing API
@@ -153,7 +159,8 @@ Feature: accept/decline shares coming from internal users
 
   @smokeTest @issue-2128 @issue-2540
   Scenario: decline an accepted share
-    Given user "Alice" has shared folder "/PARENT" with user "Brian"
+    Given user "Brian" has disabled auto-accepting
+    And user "Alice" has shared folder "/PARENT" with user "Brian"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian"
     And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
@@ -181,7 +188,9 @@ Feature: accept/decline shares coming from internal users
 
   @issue-2540
   Scenario: only one user in a group accepts a share
-    Given user "Alice" has shared folder "/PARENT" with group "grp1"
+    Given user "Brian" has disabled auto-accepting
+    And user "Carol" has disabled auto-accepting
+    And user "Alice" has shared folder "/PARENT" with group "grp1"
     And user "Alice" has shared file "/textfile0.txt" with group "grp1"
     When user "Brian" accepts share "/PARENT" offered by user "Alice" using the sharing API
     And user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
@@ -206,7 +215,8 @@ Feature: accept/decline shares coming from internal users
 
   @issue-2131
   Scenario: receive two shares with identical names from different users, accept one by one
-    Given user "Alice" has created folder "/shared"
+    Given user "Carol" has disabled auto-accepting
+    And user "Alice" has created folder "/shared"
     And user "Alice" has created folder "/shared/Alice"
     And user "Brian" has created folder "/shared"
     And user "Brian" has created folder "/shared/Brian"
@@ -226,6 +236,7 @@ Feature: accept/decline shares coming from internal users
 
   @issue-2540
   Scenario: share with a group that you are part of yourself
+    Given user "Brian" has disabled auto-accepting
     When user "Alice" shares folder "/PARENT" with group "grp1" using the sharing API
     Then the OCS status code should be "100"
     And the HTTP status code should be "200"
@@ -236,18 +247,16 @@ Feature: accept/decline shares coming from internal users
 
 
   Scenario: user accepts file that was initially accepted from another user and then declined
-    Given user "Alice" has uploaded file with content "First file" to "/testfile.txt"
+    Given user "Carol" has disabled auto-accepting
+    And user "Alice" has uploaded file with content "First file" to "/testfile.txt"
     And user "Brian" has uploaded file with content "Second file" to "/testfile.txt"
     And user "Carol" has created folder "Shares"
     And user "Carol" has uploaded file with content "Third file" to "/Shares/testfile.txt"
     And user "Alice" has shared file "/testfile.txt" with user "Carol"
-    And user "Carol" has accepted share "/testfile.txt" offered by user "Alice"
     When user "Carol" declines share "/Shares/testfile (2).txt" offered by user "Alice" using the sharing API
     And user "Brian" shares file "/testfile.txt" with user "Carol" using the sharing API
-    And user "Carol" accepts share "/testfile.txt" offered by user "Brian" using the sharing API
-    And user "Carol" accepts share "/testfile (2).txt" offered by user "Alice" using the sharing API
-    Then the OCS status code of responses on all endpoints should be "100"
-    And the HTTP status code of responses on all endpoints should be "200"
+    Then the HTTP status code should be "200"
+    And the OCS status code should be "100"
     And the sharing API should report to user "Carol" that these shares are in the accepted state
       | path                         |
       | /Shares/testfile (2).txt     |
@@ -258,7 +267,8 @@ Feature: accept/decline shares coming from internal users
 
 
   Scenario: user accepts shares received from multiple users with the same name when auto-accept share is disabled
-    Given user "David" has been created with default attributes and without skeleton files
+    Given user "Alice" has disabled auto-accepting
+    And user "David" has been created with default attributes and without skeleton files
     And user "David" has created folder "PARENT"
     And user "Brian" has shared folder "/PARENT" with user "Alice"
     And user "Carol" has created folder "PARENT"
@@ -285,7 +295,8 @@ Feature: accept/decline shares coming from internal users
 
 
   Scenario: user shares folder with matching folder-name for both user involved in sharing
-    Given user "Alice" has uploaded file with content "uploaded content" to "/PARENT/abc.txt"
+    Given user "Brian" has disabled auto-accepting
+    And user "Alice" has uploaded file with content "uploaded content" to "/PARENT/abc.txt"
     And user "Alice" has uploaded file with content "uploaded content" to "/FOLDER/abc.txt"
     When user "Alice" shares folder "/PARENT" with user "Brian" using the sharing API
     And user "Alice" shares folder "/FOLDER" with user "Brian" using the sharing API
@@ -308,7 +319,9 @@ Feature: accept/decline shares coming from internal users
 
 
   Scenario: user shares folder in a group with matching folder-name for every users involved
-    Given user "Alice" has uploaded file with content "uploaded content" to "/PARENT/abc.txt"
+    Given user "Brian" has disabled auto-accepting
+    And user "Carol" has disabled auto-accepting
+    And user "Alice" has uploaded file with content "uploaded content" to "/PARENT/abc.txt"
     And user "Alice" has uploaded file with content "uploaded content" to "/FOLDER/abc.txt"
     And user "Carol" has created folder "PARENT"
     And user "Carol" has created folder "FOLDER"
@@ -347,7 +360,9 @@ Feature: accept/decline shares coming from internal users
 
 
   Scenario: user shares files in a group with matching file-names for every users involved in sharing
-    Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile1.txt"
+    Given user "Brian" has disabled auto-accepting
+    And user "Carol" has disabled auto-accepting
+    And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "textfile1.txt"
     And user "Brian" has uploaded file "filesForUpload/textfile.txt" to "textfile1.txt"
     And user "Carol" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt"
     And user "Carol" has uploaded file "filesForUpload/textfile.txt" to "textfile1.txt"
@@ -372,6 +387,7 @@ Feature: accept/decline shares coming from internal users
 
 
   Scenario: user shares resource with matching resource-name with another user when auto accept is disabled
+    Given user "Brian" has disabled auto-accepting
     When user "Alice" shares folder "/PARENT" with user "Brian" using the sharing API
     And user "Alice" shares file "/textfile0.txt" with user "Brian" using the sharing API
     Then the OCS status code of responses on all endpoints should be "100"
@@ -394,7 +410,9 @@ Feature: accept/decline shares coming from internal users
 
 
   Scenario: user shares file in a group with matching filename when auto accept is disabled
-    Given user "Carol" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt"
+    Given user "Brian" has disabled auto-accepting
+    And user "Carol" has disabled auto-accepting
+    And user "Carol" has uploaded file "filesForUpload/textfile.txt" to "textfile0.txt"
     When user "Alice" shares file "/textfile0.txt" with group "grp1" using the sharing API
     Then the OCS status code should be "100"
     And the HTTP status code should be "200"
@@ -422,6 +440,7 @@ Feature: accept/decline shares coming from internal users
     Given these users have been created without skeleton files and not initialized:
       | username |
       | David    |
+    And user "David" has disabled auto-accepting
     And user "Alice" has uploaded file with content "uploaded content" to "/PARENT/abc.txt"
     When user "Alice" shares folder "/PARENT" with user "David" using the sharing API
     And user "David" accepts share "/PARENT" offered by user "Alice" using the sharing API
@@ -436,7 +455,8 @@ Feature: accept/decline shares coming from internal users
 
   @issue-1123 @issue-2540
   Scenario: deleting a share accepted file and folder
-    Given user "Alice" has shared folder "/PARENT" with user "Brian"
+    Given user "Brian" has disabled auto-accepting
+    And user "Alice" has shared folder "/PARENT" with user "Brian"
     And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" deletes file "/Shares/PARENT" using the WebDAV API
     Then the HTTP status code should be "204"
@@ -446,6 +466,7 @@ Feature: accept/decline shares coming from internal users
 
   @issue-765 @issue-2131
   Scenario: shares exist after restoring already shared file to a previous version
+    Given user "Brian" has disabled auto-accepting
     And user "Alice" has uploaded file with content "Test Content." to "/toShareFile.txt"
     And user "Alice" has uploaded file with content "Content Test Updated." to "/toShareFile.txt"
     And user "Alice" has shared file "/toShareFile.txt" with user "Brian"
@@ -457,7 +478,8 @@ Feature: accept/decline shares coming from internal users
 
   @issue-2131
   Scenario: user receives multiple group shares for matching file and folder name
-    Given group "grp2" has been created
+    Given user "Brian" has disabled auto-accepting
+    And group "grp2" has been created
     And user "Alice" has been added to group "grp2"
     And user "Brian" has been added to group "grp2"
     And user "Carol" has created folder "/PARENT"
@@ -522,7 +544,8 @@ Feature: accept/decline shares coming from internal users
 
   @issue-2131
   Scenario: group receives multiple shares from non-member for matching file and folder name
-    Given user "Brian" has been removed from group "grp1"
+    Given user "Carol" has disabled auto-accepting
+    And user "Brian" has been removed from group "grp1"
     And user "Alice" has created folder "/PaRent"
     And user "Carol" has created folder "/PARENT"
     And user "Alice" has uploaded the following files with content "subfile, from alice to grp1"

tests/acceptance/features/coreApiShareManagementToShares/acceptSharesToSharesFolder.feature

@@ -14,6 +14,7 @@ Feature: accept/decline shares coming from internal users to the Shares folder
 
   Scenario: accept an incoming file share
     Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
+    And user "Brian" has disabled auto-accepting
     And user "Alice" has shared file "/textfile0.txt" with user "Brian"
     When user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
     Then the OCS status code should be "100"
@@ -23,6 +24,7 @@ Feature: accept/decline shares coming from internal users to the Shares folder
 
   Scenario: accept an incoming folder share
     Given user "Alice" has created folder "/PARENT"
+    And user "Brian" has disabled auto-accepting
     And user "Alice" has uploaded file with content "ownCloud test text file parent" to "PARENT/parent.txt"
     And user "Alice" has shared file "/PARENT" with user "Brian"
     When user "Brian" accepts share "/PARENT" offered by user "Alice" using the sharing API
@@ -31,6 +33,7 @@ Feature: accept/decline shares coming from internal users to the Shares folder
 
   Scenario: accept an incoming file share and check the response
     Given user "Alice" has uploaded file with content "ownCloud test text file 0" to "textfile0.txt"
+    And user "Brian" has disabled auto-accepting
     And user "Alice" has shared file "/textfile0.txt" with user "Brian"
     When user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
     Then the OCS status code should be "100"
@@ -52,6 +55,7 @@ Feature: accept/decline shares coming from internal users to the Shares folder
 
   Scenario: accept an incoming folder share and check the response
     Given user "Alice" has created folder "/PARENT"
+    And user "Brian" has disabled auto-accepting
     And user "Alice" has uploaded file with content "ownCloud test text file parent" to "PARENT/parent.txt"
     And user "Alice" has shared file "/PARENT" with user "Brian"
     When user "Brian" accepts share "/PARENT" offered by user "Alice" using the sharing API

tests/acceptance/features/coreApiShareManagementToShares/mergeShare.feature

@@ -9,6 +9,7 @@ Feature: sharing
       | Brian    |
     And group "grp1" has been created
     And user "Brian" has been added to group "grp1"
+    And user "Brian" has disabled auto-accepting
 
   @smokeTest
   Scenario: merging shares for recipient when shared from outside with group and member

tests/acceptance/features/coreApiShareManagementToShares/moveReceivedShare.feature

@@ -16,8 +16,6 @@ Feature: sharing
     And user "Carol" has been added to group "grp1"
     And user "Alice" has created folder "/TMP"
     When user "Alice" shares folder "TMP" with group "grp1" using the sharing API
-    And user "Brian" accepts share "/TMP" offered by user "Alice" using the sharing API
-    And user "Carol" accepts share "/TMP" offered by user "Alice" using the sharing API
     And user "Brian" moves folder "/Shares/TMP" to "/Shares/new" using the WebDAV API
     And the administrator deletes user "Carol" using the provisioning API
     Then the OCS status code of responses on all endpoints should be "100"
@@ -30,8 +28,6 @@ Feature: sharing
     Given user "Alice" has uploaded file with content "foo" to "/sharefile.txt"
     And user "Alice" has shared file "/sharefile.txt" with user "Brian"
     And user "Alice" has shared file "/sharefile.txt" with user "Carol"
-    And user "Brian" has accepted share "/sharefile.txt" offered by user "Alice"
-    And user "Carol" has accepted share "/sharefile.txt" offered by user "Alice"
     When user "Carol" moves file "/Shares/sharefile.txt" to "/Shares/renamedsharefile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Carol" file "/Shares/renamedsharefile.txt" should exist
@@ -43,7 +39,6 @@ Feature: sharing
     Given user "Alice" has created folder "folderToShare"
     And user "Alice" has uploaded file with content "thisIsAFileInsideTheSharedFolder" to "/folderToShare/fileInside"
     And user "Alice" has shared folder "folderToShare" with user "Brian" with permissions "share,read,change"
-    And user "Brian" has accepted share "/folderToShare" offered by user "Alice"
     When user "Brian" moves folder "/Shares/folderToShare" to "/Shares/myFolder" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" folder "/Shares/myFolder" should exist
@@ -59,7 +54,6 @@ Feature: sharing
     Given user "Alice" has created folder "folderToShare"
     And user "Alice" has uploaded file with content "thisIsAFileInsideTheSharedFolder" to "/folderToShare/fileInside"
     And user "Alice" has shared folder "folderToShare" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/folderToShare" offered by user "Alice"
     When user "Brian" moves folder "/Shares/folderToShare" to "/Shares/myFolder" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" folder "/Shares/myFolder" should exist
@@ -73,7 +67,6 @@ Feature: sharing
   Scenario: receiver renames a received folder share to a different name on the same folder
     Given user "Alice" has created folder "PARENT"
     And user "Alice" has shared folder "PARENT" with user "Brian"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" moves folder "/Shares/PARENT" to "/Shares/myFolder" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" folder "/Shares/myFolder" should exist
@@ -83,7 +76,6 @@ Feature: sharing
   Scenario: receiver renames a received file share to different name on the same folder
     Given user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToShare.txt"
     And user "Alice" has shared file "fileToShare.txt" with user "Brian"
-    And user "Brian" has accepted share "/fileToShare.txt" offered by user "Alice"
     When user "Brian" moves file "/Shares/fileToShare.txt" to "/Shares/newFile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" file "/Shares/newFile.txt" should exist
@@ -95,7 +87,6 @@ Feature: sharing
     And user "Brian" has been added to group "grp1"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToShare.txt"
     And user "Alice" has shared file "fileToShare.txt" with group "grp1"
-    And user "Brian" has accepted share "/fileToShare.txt" offered by user "Alice"
     When user "Brian" moves file "/Shares/fileToShare.txt" to "/Shares/newFile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" file "/Shares/newFile.txt" should exist
@@ -107,7 +98,6 @@ Feature: sharing
     And user "Alice" has created folder "PARENT"
     And user "Brian" has been added to group "grp1"
     And user "Alice" has shared folder "PARENT" with group "grp1"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" moves folder "/Shares/PARENT" to "/Shares/myFolder" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" folder "/Shares/myFolder" should exist
@@ -119,7 +109,6 @@ Feature: sharing
     And user "Brian" has been added to group "grp1"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToShare.txt"
     And user "Alice" has shared file "fileToShare.txt" with group "grp1" with permissions "read,update,share"
-    And user "Brian" has accepted share "/fileToShare.txt" offered by user "Alice"
     When user "Brian" moves folder "/Shares/fileToShare.txt" to "/Shares/newFile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" file "/Shares/newFile.txt" should exist
@@ -131,7 +120,6 @@ Feature: sharing
     And user "Alice" has created folder "PARENT"
     And user "Brian" has been added to group "grp1"
     And user "Alice" has shared folder "PARENT" with group "grp1" with permissions "share,read,change"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" moves folder "/Shares/PARENT" to "/Shares/myFolder" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" folder "/Shares/myFolder" should exist
@@ -143,7 +131,6 @@ Feature: sharing
     And user "Brian" has been added to group "grp1"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "fileToShare.txt"
     And user "Alice" has shared file "fileToShare.txt" with group "grp1" with permissions "share,read"
-    And user "Brian" has accepted share "/fileToShare.txt" offered by user "Alice"
     When user "Brian" moves file "/Shares/fileToShare.txt" to "/Shares/newFile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" file "/Shares/newFile.txt" should exist
@@ -155,7 +142,6 @@ Feature: sharing
     And user "Alice" has created folder "PARENT"
     And user "Brian" has been added to group "grp1"
     And user "Alice" has shared folder "PARENT" with group "grp1" with permissions "share,read"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" moves folder "/Shares/PARENT" to "/Shares/myFolder" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" folder "/Shares/myFolder" should exist
@@ -168,13 +154,11 @@ Feature: sharing
     And user "Alice" has created folder "<sharer_folder>"
     And user "Alice" has created folder "<group_folder>"
     And user "Alice" has shared folder "<sharer_folder>" with user "Brian"
-    And user "Brian" has accepted share "/<sharer_folder>" offered by user "Alice"
     When user "Brian" moves folder "/Shares/<sharer_folder>" to "/Shares/<receiver_folder>" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Alice" folder "<receiver_folder>" should not exist
     And as "Brian" folder "/Shares/<receiver_folder>" should exist
     When user "Alice" shares folder "<group_folder>" with group "grp1" using the sharing API
-    And user "Carol" accepts share "/<group_folder>" offered by user "Alice" using the sharing API
     And user "Carol" moves folder "/Shares/<group_folder>" to "/Shares/<receiver_folder>" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Alice" folder "<receiver_folder>" should not exist
@@ -193,13 +177,11 @@ Feature: sharing
     And user "Alice" has uploaded file with content "thisIsAFileInsideTheSharedFolder" to "/<sharer_folder>/fileInside"
     And user "Alice" has uploaded file with content "thisIsAFileInsideTheSharedFolder" to "/<group_folder>/fileInside"
     And user "Alice" has shared folder "<sharer_folder>" with user "Brian" with permissions "share,read,change"
-    And user "Brian" has accepted share "/<sharer_folder>" offered by user "Alice"
     When user "Brian" moves folder "/Shares/<sharer_folder>/fileInside" to "/Shares/<sharer_folder>/<receiver_file>" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Alice" file "<sharer_folder>/<receiver_file>" should exist
     And as "Brian" file "/Shares/<sharer_folder>/<receiver_file>" should exist
     When user "Alice" shares folder "<group_folder>" with group "grp1" with permissions "share,read,change" using the sharing API
-    And user "Carol" accepts share "/<group_folder>" offered by user "Alice" using the sharing API
     And user "Carol" moves folder "/Shares/<group_folder>/fileInside" to "/Shares/<group_folder>/<receiver_file>" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Alice" file "<group_folder>/<receiver_file>" should exist

tests/acceptance/features/coreApiShareManagementToShares/moveShareInsideAnotherShare.feature

@@ -15,8 +15,6 @@ Feature: moving a share inside another share
     And user "Alice" has uploaded file with content "text B" to "/folderB/fileB.txt"
     And user "Alice" has shared folder "folderA" with user "Brian"
     And user "Alice" has shared folder "folderB" with user "Brian"
-    And user "Brian" has accepted share "/folderA" offered by user "Alice"
-    And user "Brian" has accepted share "/folderB" offered by user "Alice"
 
 
   Scenario: share receiver cannot move a whole share inside another share

tests/acceptance/features/coreApiShareOperationsToShares1/accessToShare.feature

@@ -14,7 +14,6 @@ Feature: sharing
   Scenario Outline: sharee can see the share
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" gets all the shares shared with him using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -30,8 +29,6 @@ Feature: sharing
     And user "Alice" has uploaded file with content "some data" to "/textfile1.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
     And user "Alice" has shared file "textfile1.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
-    And user "Brian" has accepted share "/textfile1.txt" offered by user "Alice"
     When user "Brian" gets all the shares shared with him that are received as file "/Shares/textfile1.txt" using the provisioning API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -47,8 +44,6 @@ Feature: sharing
     And user "Alice" has uploaded file with content "some data" to "/textfile1.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
     And user "Alice" has shared file "textfile1.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
-    And user "Brian" has accepted share "/textfile1.txt" offered by user "Alice"
     When user "Brian" gets all the shares shared with him that are received as file "/Shares/textfile0.txt" using the provisioning API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -64,7 +59,6 @@ Feature: sharing
     And group "grp1" has been created
     And user "Brian" has been added to group "grp1"
     And user "Alice" has shared file "textfile0.txt" with group "grp1"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" gets all the shares shared with him using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"

tests/acceptance/features/coreApiShareOperationsToShares1/changingFilesShare.feature

@@ -15,7 +15,6 @@ Feature: sharing
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/shared"
     And user "Alice" has shared folder "/shared" with user "Brian"
-    And user "Brian" has accepted share "/shared" offered by user "Alice"
     And user "Brian" has uploaded file with content "some data" to "/textfile0.txt"
     When user "Brian" moves file "textfile0.txt" to "/Shares/shared/shared_file.txt" using the WebDAV API
     Then the HTTP status code should be "201"
@@ -35,8 +34,6 @@ Feature: sharing
     And user "Alice" has moved file "textfile0.txt" to "share1/textfile0.txt"
     And user "Alice" has shared folder "/share1" with user "Brian"
     And user "Alice" has shared folder "/share2" with user "Brian"
-    And user "Brian" has accepted share "/share1" offered by user "Alice"
-    And user "Brian" has accepted share "/share2" offered by user "Alice"
     When user "Brian" moves file "/Shares/share1/textfile0.txt" to "/Shares/share2/textfile0.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" file "/Shares/share1/textfile0.txt" should not exist
@@ -56,8 +53,6 @@ Feature: sharing
     And user "Brian" has uploaded file with content "some data" to "/textfile0.txt"
     And user "Alice" has shared folder "/share1" with user "Brian"
     And user "Alice" has shared folder "/share2" with user "Brian"
-    And user "Brian" has accepted share "/share1" offered by user "Alice"
-    And user "Brian" has accepted share "/share2" offered by user "Alice"
     When user "Brian" moves file "textfile0.txt" to "/Shares/share1/shared_file.txt" using the WebDAV API
     And user "Brian" moves file "/Shares/share1/shared_file.txt" to "/Shares/share2/shared_file.txt" using the WebDAV API
     Then the HTTP status code of responses on all endpoints should be "201"
@@ -80,8 +75,6 @@ Feature: sharing
     And user "Alice" has moved file "textfile0.txt" to "PARENT/shared_file.txt"
     And user "Alice" has shared folder "/PARENT" with user "Carol"
     And user "Brian" has shared folder "/PARENT" with user "Carol"
-    And user "Carol" has accepted share "/PARENT" offered by user "Alice"
-    And user "Carol" has accepted share "/PARENT" offered by user "Brian"
     When user "Carol" moves file "/Shares/PARENT/shared_file.txt" to "/Shares/PARENT (2)/shared_file.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Carol" file "/Shares/PARENT (2)/shared_file.txt" should exist
@@ -97,7 +90,6 @@ Feature: sharing
     Given using <dav-path-version> DAV path
     And user "Alice" has uploaded file with content "this is the old content" to "/textfile1.txt"
     And user "Alice" has shared file "/textfile1.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile1.txt" offered by user "Alice"
     When user "Brian" uploads file with content "this is a new content" to "/Shares/textfile1.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And as "Brian" file "Shares/textfile1.txt" should exist

tests/acceptance/features/coreApiShareOperationsToShares1/gettingShares.feature

@@ -14,7 +14,6 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "some data" to "/file_to_share.txt"
     And user "Alice" has shared file "file_to_share.txt" with user "Brian"
-    And user "Brian" has accepted share "/file_to_share.txt" offered by user "Alice"
     When user "Alice" gets all shares shared by her using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -29,7 +28,6 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When the administrator gets all shares shared by him using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -49,8 +47,6 @@ Feature: sharing
     And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
     And user "Alice" has shared file "textfile0.txt" with user "Carol"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
-    And user "Carol" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Alice" gets all the shares of the file "textfile0.txt" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -71,9 +67,7 @@ Feature: sharing
       | David    |
     And user "Alice" has uploaded file with content "some data" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Brian" has shared file "/Shares/textfile0.txt" with user "Carol"
-    And user "Carol" has accepted share "/textfile0.txt" offered by user "Brian"
     When user "Alice" gets all the shares with reshares of the file "textfile0.txt" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -94,7 +88,6 @@ Feature: sharing
     And user "Carol" has created folder "/shared"
     And user "Carol" has uploaded file with content "some data" to "/shared/shared_file.txt"
     And user "Carol" has shared folder "/shared" with user "Brian"
-    And user "Brian" has accepted share "/shared" offered by user "Carol"
     And user "Brian" has shared folder "/Shares/shared" with group "grp1"
     # no need to accept this share as it is Carol's file
     When user "Carol" gets all the shares shared with her using the sharing API
@@ -111,7 +104,6 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "some data" to "/file_to_share.txt"
     And user "Alice" has shared file "file_to_share.txt" with user "Brian"
-    And user "Brian" has accepted share "/file_to_share.txt" offered by user "Alice"
     When user "Alice" gets the info of the last share using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -161,8 +153,6 @@ Feature: sharing
     And user "Alice" has created folder "/PARENT"
     And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
     And user "Alice" has shared folder "/PARENT" with group "group0"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
-    And user "Carol" has accepted share "/PARENT" offered by user "Alice"
     When the administrator removes user "Carol" from group "group0" using the provisioning API
     Then the HTTP status code should be "200"
     And user "Brian" should see the following elements
@@ -178,7 +168,6 @@ Feature: sharing
     And user "Alice" has created folder "/PARENT"
     And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
     And user "Alice" has shared file "PARENT/parent.txt" with user "Brian"
-    And user "Brian" has accepted share "/parent.txt" offered by user "Alice"
     When user "Alice" gets all the shares inside the folder "PARENT" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"

tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesPendingFiltered.feature

@@ -9,6 +9,7 @@ Feature: get the pending shares filtered by type (user, group etc)
       | Alice    |
       | Brian    |
     And group "grp1" has been created
+    And user "Brian" has disabled auto-accepting
     And user "Brian" has been added to group "grp1"
     And user "Alice" has created folder "/folderToShareWithUser"
     And user "Alice" has created folder "/folderToShareWithGroup"
@@ -22,9 +23,7 @@ Feature: get the pending shares filtered by type (user, group etc)
       | path        | /folderToShareWithPublic |
       | permissions | read                     |
     And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
-    And user "Brian" has accepted share "/fileToShareWithUser.txt" offered by user "Alice"
     And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
-    And user "Brian" has accepted share "/fileToShareWithGroup.txt" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /fileToShareWithPublic.txt |
       | permissions | read                       |

tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFiltered.feature

@@ -17,16 +17,12 @@ Feature: get the received shares filtered by type (user, group etc)
     And user "Alice" has uploaded file with content "file to share with group" to "/fileToShareWithGroup.txt"
     And user "Alice" has uploaded file with content "file to share with public" to "/fileToShareWithPublic.txt"
     And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
-    And user "Brian" has accepted share "/folderToShareWithUser" offered by user "Alice"
     And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
-    And user "Brian" has accepted share "/folderToShareWithGroup" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /folderToShareWithPublic |
       | permissions | read                     |
     And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
-    And user "Brian" has accepted share "/fileToShareWithUser.txt" offered by user "Alice"
     And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
-    And user "Brian" has accepted share "/fileToShareWithGroup.txt" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /fileToShareWithPublic.txt |
       | permissions | read                       |

tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesReceivedFilteredEmpty.feature

@@ -21,12 +21,10 @@ Feature: get the received shares filtered by type (user, group etc)
   Scenario Outline: getting shares received from users when there are none
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
-    And user "Brian" has accepted share "/folderToShareWithGroup" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /folderToShareWithPublic |
       | permissions | read                     |
     And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
-    And user "Brian" has accepted share "/fileToShareWithGroup.txt" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /fileToShareWithPublic.txt |
       | permissions | read                       |
@@ -43,12 +41,10 @@ Feature: get the received shares filtered by type (user, group etc)
   Scenario Outline: getting shares received from groups when there are none
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
-    And user "Brian" has accepted share "/folderToShareWithUser" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /folderToShareWithPublic |
       | permissions | read                     |
     And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
-    And user "Brian" has accepted share "/fileToShareWithUser.txt" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /fileToShareWithPublic.txt |
       | permissions | read                       |
@@ -68,16 +64,12 @@ Feature: get the received shares filtered by type (user, group etc)
     #       that are "shared with me" should always return an empty list.
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
-    And user "Brian" has accepted share "/folderToShareWithUser" offered by user "Alice"
     And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
-    And user "Brian" has accepted share "/folderToShareWithGroup" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /folderToShareWithPublic |
       | permissions | read                     |
     And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
-    And user "Brian" has accepted share "/fileToShareWithUser.txt" offered by user "Alice"
     And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
-    And user "Brian" has accepted share "/fileToShareWithGroup.txt" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /fileToShareWithPublic.txt |
       | permissions | read                       |

tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFiltered.feature

@@ -17,16 +17,12 @@ Feature: get shares filtered by type (user, group etc)
     And user "Alice" has uploaded file with content "file to share with group" to "/fileToShareWithGroup.txt"
     And user "Alice" has uploaded file with content "file to share with public" to "/fileToShareWithPublic.txt"
     And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
-    And user "Brian" has accepted share "/folderToShareWithUser" offered by user "Alice"
     And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
-    And user "Brian" has accepted share "/folderToShareWithGroup" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /folderToShareWithPublic |
       | permissions | read                     |
     And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
-    And user "Brian" has accepted share "/fileToShareWithUser.txt" offered by user "Alice"
     And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
-    And user "Brian" has accepted share "/fileToShareWithGroup.txt" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /fileToShareWithPublic.txt |
       | permissions | read                       |

tests/acceptance/features/coreApiShareOperationsToShares1/gettingSharesSharedFilteredEmpty.feature

@@ -21,12 +21,10 @@ Feature: get shares filtered by type (user, group etc)
   Scenario Outline: getting shares shared to users when there are none
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
-    And user "Brian" has accepted share "/folderToShareWithGroup" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /folderToShareWithPublic |
       | permissions | read                     |
     And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
-    And user "Brian" has accepted share "/fileToShareWithGroup.txt" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /fileToShareWithPublic.txt |
       | permissions | read                       |
@@ -43,12 +41,10 @@ Feature: get shares filtered by type (user, group etc)
   Scenario Outline: getting shares shared to groups when there are none
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
-    And user "Brian" has accepted share "/folderToShareWithUser" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /folderToShareWithPublic |
       | permissions | read                     |
     And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
-    And user "Brian" has accepted share "/fileToShareWithUser.txt" offered by user "Alice"
     And user "Alice" has created a public link share with settings
       | path        | /fileToShareWithPublic.txt |
       | permissions | read                       |
@@ -65,13 +61,9 @@ Feature: get shares filtered by type (user, group etc)
   Scenario Outline: getting shares shared to public links when there are none
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/folderToShareWithUser" with user "Brian"
-    And user "Brian" has accepted share "/folderToShareWithUser" offered by user "Alice"
     And user "Alice" has shared folder "/folderToShareWithGroup" with group "grp1"
-    And user "Brian" has accepted share "/folderToShareWithGroup" offered by user "Alice"
     And user "Alice" has shared file "/fileToShareWithUser.txt" with user "Brian"
-    And user "Brian" has accepted share "/fileToShareWithUser.txt" offered by user "Alice"
     And user "Alice" has shared file "/fileToShareWithGroup.txt" with group "grp1"
-    And user "Brian" has accepted share "/fileToShareWithGroup.txt" offered by user "Alice"
     When user "Alice" gets the public link shares shared by her using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"

tests/acceptance/features/coreApiShareOperationsToShares2/getWebDAVSharePermissions.feature

@@ -34,7 +34,6 @@ Feature: sharing
     Given using <dav-path-version> DAV path
     And user "Alice" has uploaded file with content "foo" to "/tmp.txt"
     And user "Alice" has shared file "/tmp.txt" with user "Brian"
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Brian" gets the following properties of file "/Shares/tmp.txt" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -56,7 +55,6 @@ Feature: sharing
       | shareType   | group             |
       | permissions | share,update,read |
       | shareWith   | grp1              |
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Brian" gets the following properties of file "/Shares/tmp.txt" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -72,7 +70,6 @@ Feature: sharing
     Given using <dav-path-version> DAV path
     And user "Alice" has uploaded file with content "foo" to "/tmp.txt"
     And user "Alice" has shared file "tmp.txt" with user "Brian"
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | update,read |
     Then the HTTP status code should be "200"
@@ -93,7 +90,6 @@ Feature: sharing
       | shareType   | group       |
       | permissions | update,read |
       | shareWith   | grp1        |
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Brian" gets the following properties of file "/Shares/tmp.txt" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -109,7 +105,6 @@ Feature: sharing
     Given using <dav-path-version> DAV path
     And user "Alice" has uploaded file with content "foo" to "/tmp.txt"
     And user "Alice" has shared file "tmp.txt" with user "Brian"
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,read |
     Then the HTTP status code should be "200"
@@ -130,7 +125,6 @@ Feature: sharing
       | shareType   | group      |
       | permissions | share,read |
       | shareWith   | grp1       |
-    And user "Brian" has accepted share "/tmp.txt" offered by user "Alice"
     When user "Brian" gets the following properties of file "/Shares/tmp.txt" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -165,7 +159,6 @@ Feature: sharing
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/tmp"
     And user "Alice" has shared file "/tmp" with user "Brian"
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/Shares/tmp" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -186,7 +179,6 @@ Feature: sharing
       | path      | tmp   |
       | shareType | group |
       | shareWith | grp1  |
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/Shares/tmp" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -202,7 +194,6 @@ Feature: sharing
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/tmp"
     And user "Alice" has shared file "/tmp" with user "Brian"
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,delete,create,read |
     Then the HTTP status code should be "200"
@@ -223,7 +214,6 @@ Feature: sharing
       | shareType   | group                    |
       | shareWith   | grp1                     |
       | permissions | share,delete,create,read |
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/Shares/tmp" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -239,7 +229,6 @@ Feature: sharing
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/tmp"
     And user "Alice" has shared file "/tmp" with user "Brian"
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,delete,update,read |
     Then the HTTP status code should be "200"
@@ -260,7 +249,6 @@ Feature: sharing
       | shareType   | group                    |
       | shareWith   | grp1                     |
       | permissions | share,delete,update,read |
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/Shares/tmp" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -276,7 +264,6 @@ Feature: sharing
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/tmp"
     And user "Alice" has shared file "/tmp" with user "Brian"
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,create,update,read |
     Then the HTTP status code should be "200"
@@ -297,7 +284,6 @@ Feature: sharing
       | shareType   | group                    |
       | shareWith   | grp1                     |
       | permissions | share,create,update,read |
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/Shares/tmp" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |
@@ -313,7 +299,6 @@ Feature: sharing
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/tmp"
     And user "Alice" has shared file "/tmp" with user "Brian"
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | change |
     Then the HTTP status code should be "200"
@@ -334,7 +319,6 @@ Feature: sharing
       | shareType   | group  |
       | shareWith   | grp1   |
       | permissions | change |
-    And user "Brian" has accepted share "/tmp" offered by user "Alice"
     When user "Brian" gets the following properties of folder "/Shares/tmp" using the WebDAV API
       | propertyName          |
       | ocs:share-permissions |

tests/acceptance/features/coreApiShareOperationsToShares2/shareAccessByID.feature

@@ -14,7 +14,6 @@ Feature: share access by ID
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API
-    And user "Brian" accepts share "/textfile0.txt" offered by user "Alice" using the sharing API
     And user "Alice" gets share with id "%last_share_id%" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
@@ -59,7 +58,6 @@ Feature: share access by ID
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API
-    And user "Brian" accepts share with ID "%last_share_id%" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
     And user "Brian" should see the following elements
@@ -75,7 +73,6 @@ Feature: share access by ID
 
   Scenario Outline: accept a share using the invalid share Id
     Given using OCS API version "<ocs_api_version>"
-    When user "Brian" accepts share with ID "<share_id>" using the sharing API
     Then the OCS status code should be "404"
     And the HTTP status code should be "<http_status_code>"
     And the API should not return any data
@@ -93,7 +90,6 @@ Feature: share access by ID
 
   Scenario Outline: accept a share using empty share Id
     Given using OCS API version "<ocs_api_version>"
-    When user "Brian" accepts share with ID "" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "<http_status_code>"
     And the API should not return any data
@@ -107,7 +103,6 @@ Feature: share access by ID
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" declines share with ID "%last_share_id%" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"

tests/acceptance/features/coreApiShareOperationsToShares2/uploadToShare.feature

@@ -15,7 +15,6 @@ Feature: sharing
       | shareType   | user   |
       | permissions | read   |
       | shareWith   | Brian  |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "403"
     And as "Alice" file "/FOLDER/textfile.txt" should not exist
@@ -32,7 +31,6 @@ Feature: sharing
       | shareType   | group  |
       | permissions | read   |
       | shareWith   | grp1   |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "403"
     And as "Alice" file "/FOLDER/textfile.txt" should not exist
@@ -51,7 +49,6 @@ Feature: sharing
       | shareType   | user   |
       | permissions | create |
       | shareWith   | Brian  |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the following headers should match these regular expressions for user "Brian"
@@ -79,7 +76,6 @@ Feature: sharing
       | shareType   | group  |
       | permissions | create |
       | shareWith   | grp1   |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the following headers should match these regular expressions for user "Brian"
@@ -105,7 +101,6 @@ Feature: sharing
       | shareType   | user   |
       | permissions | change |
       | shareWith   | Brian  |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/FOLDER/textfile.txt" for user "Alice" should be:
@@ -131,7 +126,6 @@ Feature: sharing
       | shareType   | group  |
       | permissions | change |
       | shareWith   | grp1   |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/textfile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/FOLDER/textfile.txt" for user "Alice" should be:
@@ -152,7 +146,6 @@ Feature: sharing
     And the quota of user "Brian" has been set to "0"
     And user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/myfile.txt"
     And user "Alice" has shared file "myfile.txt" with user "Brian"
-    And user "Brian" has accepted share "/myfile.txt" offered by user "Alice"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/myfile.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And the following headers should match these regular expressions for user "Brian"
@@ -178,7 +171,6 @@ Feature: sharing
       | shareType   | user   |
       | permissions | change |
       | shareWith   | Brian  |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And the quota of user "Alice" has been set to "0"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API
     Then the HTTP status code should be "507"
@@ -200,7 +192,6 @@ Feature: sharing
       | shareType   | group  |
       | permissions | change |
       | shareWith   | grp1   |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And the quota of user "Alice" has been set to "0"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API
     Then the HTTP status code should be "507"
@@ -220,7 +211,6 @@ Feature: sharing
       | shareType   | user   |
       | permissions | create |
       | shareWith   | Brian  |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And the quota of user "Alice" has been set to "0"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API
     Then the HTTP status code should be "507"
@@ -242,7 +232,6 @@ Feature: sharing
       | shareType   | group  |
       | permissions | create |
       | shareWith   | grp1   |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And the quota of user "Alice" has been set to "0"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/FOLDER/myfile.txt" using the WebDAV API
     Then the HTTP status code should be "507"
@@ -262,7 +251,6 @@ Feature: sharing
       | shareType   | user          |
       | permissions | <permissions> |
       | shareWith   | Brian         |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file with content "some content" to "/Shares/FOLDER/textFile.txt" using the WebDAV API
     And user "Alice" downloads file "/FOLDER/textFile.txt" using the WebDAV API
     Then the HTTP status code should be "200"
@@ -278,7 +266,6 @@ Feature: sharing
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Brian" has created folder "/folder-to-share"
     And user "Brian" has shared folder "/folder-to-share" with user "Alice"
-    And user "Alice" has accepted share "/folder-to-share" offered by user "Brian"
     When user "Alice" uploads file "filesForUpload/zerobyte.txt" to "/Shares/folder-to-share/zerobyte.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Alice" file "/Shares/folder-to-share/zerobyte.txt" should exist

tests/acceptance/features/coreApiSharePublicLink2/reShareAsPublicLinkToSharesNewDav.feature

@@ -14,7 +14,6 @@ Feature: reshare as public link
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has created folder "/test"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "read"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     When user "Brian" creates a public link share using the sharing API with settings
       | path         | /Shares/test |
       | publicUpload | false        |
@@ -31,7 +30,6 @@ Feature: reshare as public link
     And user "Alice" has created folder "/test"
     And user "Alice" has uploaded file with content "some content" to "/test/file.txt"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     When user "Brian" creates a public link share using the sharing API with settings
       | path         | /Shares/test |
       | publicUpload | false        |
@@ -51,7 +49,6 @@ Feature: reshare as public link
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has created folder "/test"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     When user "Brian" creates a public link share using the sharing API with settings
       | path         | /Shares/test              |
       | permissions  | read,update,create,delete |
@@ -68,7 +65,6 @@ Feature: reshare as public link
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has created folder "/test"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "change"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     When user "Brian" creates a public link share using the sharing API with settings
       | path         | /Shares/test |
       | publicUpload | true         |
@@ -85,7 +81,6 @@ Feature: reshare as public link
     And user "Alice" has created folder "/test"
     And user "Alice" has uploaded file with content "some content" to "/test/file.txt"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     When user "Brian" creates a public link share using the sharing API with settings
       | path         | /Shares/test |
       | publicUpload | false        |
@@ -106,7 +101,6 @@ Feature: reshare as public link
     And user "Alice" has created folder "/test"
     And user "Alice" has uploaded file with content "some content" to "/test/file.txt"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     When user "Brian" creates a public link share using the sharing API with settings
       | path         | /Shares/test              |
       | permissions  | read,update,create,delete |
@@ -128,7 +122,6 @@ Feature: reshare as public link
     And user "Alice" has created folder "/test"
     And user "Alice" has created folder "/test/sub"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     When user "Brian" creates a public link share using the sharing API with settings
       | path         | /Shares/test/sub          |
       | permissions  | read,update,create,delete |
@@ -146,7 +139,6 @@ Feature: reshare as public link
     And user "Alice" has created folder "/test"
     And user "Alice" has created folder "/test/sub"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     And user "Brian" has created a public link share with settings
       | path         | /Shares/test |
       | permissions  | read         |
@@ -167,7 +159,6 @@ Feature: reshare as public link
     And user "Alice" has created folder "/test"
     And user "Alice" has created folder "/test/sub"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     And user "Brian" has created a public link share with settings
       | path         | /Shares/test/sub |
       | permissions  | read             |

tests/acceptance/features/coreApiSharePublicLink3/updatePublicLinkShare.feature

@@ -251,7 +251,6 @@ Feature: update a public link share
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/test"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     And user "Brian" has created a public link share with settings
       | path         | /Shares/test |
       | publicUpload | false        |
@@ -272,7 +271,6 @@ Feature: update a public link share
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/test"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     And user "Brian" has created a public link share with settings
       | path         | /Shares/test |
       | publicUpload | false        |
@@ -293,7 +291,6 @@ Feature: update a public link share
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/test"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     And user "Brian" has created a public link share with settings
       | path        | /Shares/test |
       | permissions | read         |
@@ -314,7 +311,6 @@ Feature: update a public link share
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/test"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     And user "Brian" has created a public link share with settings
       | path        | /Shares/test |
       | permissions | read         |

tests/acceptance/features/coreApiShareReshareToShares1/reShare.feature

@@ -16,7 +16,6 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" shares file "/Shares/textfile0.txt" with user "Carol" with permissions "read,update" using the sharing API
     Then the OCS status code should be "403"
     And the HTTP status code should be "<http_status_code>"
@@ -33,7 +32,6 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "read,update"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" shares folder "/Shares/FOLDER" with user "Carol" with permissions "read,update" using the sharing API
     Then the OCS status code should be "403"
     And the HTTP status code should be "<http_status_code>"
@@ -50,11 +48,9 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" shares file "/Shares/textfile0.txt" with user "Carol" with permissions "share,read" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
     And as "Carol" file "/Shares/textfile0.txt" should exist
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -66,11 +62,9 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" shares folder "/Shares/FOLDER" with user "Carol" with permissions "share,read" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Carol" should be able to accept pending share "/FOLDER" offered by user "Brian"
     And as "Carol" folder "/Shares/FOLDER" should exist
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -82,11 +76,9 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "share,update,read"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" shares file "/Shares/textfile0.txt" with user "Carol" with permissions "share,read" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
     And as "Carol" file "/Shares/textfile0.txt" should exist
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -98,11 +90,9 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "share,update,read"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" shares folder "/Shares/FOLDER" with user "Carol" with permissions "share,read" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Carol" should be able to accept pending share "/FOLDER" offered by user "Brian"
     And as "Carol" folder "/Shares/FOLDER" should exist
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -114,7 +104,6 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions 17
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" shares file "/Shares/textfile0.txt" with user "Carol" with permissions <reshare_permissions> using the sharing API
     Then the OCS status code should be "403"
     And the HTTP status code should be "<http_status_code>"
@@ -143,15 +132,13 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions <received_permissions>
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" shares file "/Shares/textfile0.txt" with user "Carol" with permissions <reshare_permissions> using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
     And the fields of the last response to user "Brian" sharing with user "Carol" should include
       | share_with  | %username%            |
       | file_target | /Shares/textfile0.txt |
-      | path        | /Shares/textfile0.txt |
+      | path        | /textfile0.txt |
       | permissions | <granted_permissions> |
       | uid_owner   | %username%            |
     And as "Carol" file "/Shares/textfile0.txt" should exist
@@ -184,7 +171,6 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has created folder "/PARENT"
     And user "Alice" has shared folder "/PARENT" with user "Brian" with permissions <received_permissions>
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" shares folder "/Shares/PARENT" with user "Carol" with permissions <reshare_permissions> using the sharing API
     Then the OCS status code should be "403"
     And the HTTP status code should be "<http_status_code>"
@@ -225,7 +211,6 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has created folder "/PARENT"
     And user "Alice" has shared folder "/PARENT" with user "Brian" with permissions <received_permissions>
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" shares folder "/Shares/PARENT" with user "Carol" with permissions <reshare_permissions> using the sharing API
     Then the OCS status code should be "403"
     And the HTTP status code should be "<http_status_code>"
@@ -254,13 +239,11 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Alice" has deleted file "textfile0.txt"
     And user "Alice" has uploaded file with content "ownCloud new test text file 0" to "/textfile0.txt"
     When user "Alice" shares file "textfile0.txt" with user "Brian" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Brian" should be able to accept pending share "/textfile0.txt" offered by user "Alice"
     And the content of file "/Shares/textfile0.txt" for user "Brian" should be "ownCloud new test text file 0"
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -272,13 +255,11 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has created folder "/PARENT"
     And user "Alice" has shared folder "PARENT" with user "Brian"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     And user "Alice" has deleted folder "PARENT"
     And user "Alice" has created folder "/PARENT"
     When user "Alice" shares folder "PARENT" with user "Brian" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Brian" should be able to accept pending share "/PARENT" offered by user "Alice"
     And as "Brian" folder "/Shares/PARENT" should exist
     Examples:
       | ocs_api_version | ocs_status_code |
@@ -290,13 +271,11 @@ Feature: sharing
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Alice" has deleted file "/textfile0.txt"
     And user "Alice" has created folder "/textfile0.txt"
     When user "Alice" shares folder "textfile0.txt" with user "Brian" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Brian" should be able to accept pending share "/textfile0.txt" offered by user "Alice"
     And as "Brian" folder "/Shares/textfile0.txt" should exist
     Examples:
       | ocs_api_version | ocs_status_code |

tests/acceptance/features/coreApiShareReshareToShares2/reShareChain.feature

@@ -14,11 +14,8 @@ Feature: resharing can be done on a reshared resource
       | David    |
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Brian" has shared file "/Shares/textfile0.txt" with user "Carol"
-    And user "Carol" has accepted share "/textfile0.txt" offered by user "Brian"
     And user "Carol" has shared file "/Shares/textfile0.txt" with user "David"
-    And user "David" has accepted share "/textfile0.txt" offered by user "Carol"
     When user "Brian" deletes file "/Shares/textfile0.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And the content of file "/Shares/textfile0.txt" for user "Carol" should be "ownCloud test text file 0"

tests/acceptance/features/coreApiShareReshareToShares2/reShareDisabled.feature

@@ -15,7 +15,6 @@ Feature: resharing can be disabled
     When user "Alice" shares file "/textfile0.txt" with user "Brian" with permissions "share,update,read" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Brian" should be able to accept pending share "/textfile0.txt" offered by user "Alice"
     And as "Brian" file "/Shares/textfile0.txt" should exist
     Examples:
       | ocs_api_version | ocs_status_code |

tests/acceptance/features/coreApiShareReshareToShares2/reShareSubfolder.feature

@@ -17,11 +17,9 @@ Feature: a subfolder of a received share can be reshared
   Scenario Outline: user is allowed to reshare a sub-folder with the same permissions
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     When user "Brian" shares folder "/Shares/TMP/SUB" with user "Carol" with permissions "share,read" using the sharing API
     Then the OCS status code should be "<ocs_status_code>"
     And the HTTP status code should be "200"
-    And user "Carol" should be able to accept pending share "/SUB" offered by user "Brian"
     And as "Carol" folder "/Shares/SUB" should exist
     And as "Brian" folder "/Shares/TMP/SUB" should exist
     Examples:
@@ -33,7 +31,6 @@ Feature: a subfolder of a received share can be reshared
   Scenario Outline: user is not allowed to reshare a sub-folder with more permissions
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions <received_permissions>
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     When user "Brian" shares folder "/Shares/TMP/SUB" with user "Carol" with permissions <reshare_permissions> using the sharing API
     Then the OCS status code should be "403"
     And the HTTP status code should be "<http_status_code>"
@@ -87,9 +84,7 @@ Feature: a subfolder of a received share can be reshared
   Scenario Outline: user is allowed to update reshare of a sub-folder with less permissions
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "/Shares/TMP/SUB" with user "Carol" with permissions "share,create,update,read"
-    And user "Carol" has accepted share "/SUB" offered by user "Brian"
     When user "Brian" updates the last share using the sharing API with
       | permissions | share,read |
     Then the OCS status code should be "<ocs_status_code>"
@@ -107,9 +102,7 @@ Feature: a subfolder of a received share can be reshared
   Scenario Outline: user is allowed to update reshare of a sub-folder to the maximum allowed permissions
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "/Shares/TMP/SUB" with user "Carol" with permissions "share,read"
-    And user "Carol" has accepted share "/SUB" offered by user "Brian"
     When user "Brian" updates the last share using the sharing API with
       | permissions | share,create,update,read |
     Then the OCS status code should be "<ocs_status_code>"
@@ -127,9 +120,7 @@ Feature: a subfolder of a received share can be reshared
   Scenario Outline: user is not allowed to update reshare of a sub-folder with more permissions
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "/Shares/TMP/SUB" with user "Carol" with permissions "share,read"
-    And user "Carol" has accepted share "/SUB" offered by user "Brian"
     When user "Brian" updates the last share using the sharing API with
       | permissions | all |
     Then the OCS status code should be "403"

tests/acceptance/features/coreApiShareReshareToShares3/reShareUpdate.feature

@@ -16,9 +16,7 @@ Feature: sharing
   Scenario Outline: update of reshare can reduce permissions
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,create,update,read"
-    And user "Carol" has accepted share "/TMP" offered by user "Brian"
     When user "Brian" updates the last share using the sharing API with
       | permissions | share,read |
     Then the OCS status code should be "<ocs_status_code>"
@@ -33,9 +31,7 @@ Feature: sharing
   Scenario Outline: update of reshare can increase permissions to the maximum allowed
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,read"
-    And user "Carol" has accepted share "/TMP" offered by user "Brian"
     When user "Brian" updates the last share using the sharing API with
       | permissions | share,create,update,read |
     Then the OCS status code should be "<ocs_status_code>"
@@ -50,9 +46,7 @@ Feature: sharing
   Scenario Outline: do not allow update of reshare to exceed permissions
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,read"
-    And user "Carol" has accepted share "/TMP" offered by user "Brian"
     When user "Brian" updates the last share using the sharing API with
       | permissions | all |
     Then the OCS status code should be "403"
@@ -67,9 +61,7 @@ Feature: sharing
   Scenario Outline: update of user reshare by the original share owner can increase permissions up to the permissions of the top-level share
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,read"
-    And user "Carol" has accepted share "/TMP" offered by user "Brian"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,create,update,read |
     Then the OCS status code should be "<ocs_status_code>"
@@ -84,9 +76,7 @@ Feature: sharing
   Scenario Outline: update of user reshare by the original share owner can increase permissions to more than the permissions of the top-level share
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,update,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,read"
-    And user "Carol" has accepted share "/TMP" offered by user "Brian"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,create,update,read |
     Then the OCS status code should be "<ocs_status_code>"
@@ -103,9 +93,7 @@ Feature: sharing
     And group "grp1" has been created
     And user "Carol" has been added to group "grp1"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "Shares/TMP" with group "grp1" with permissions "share,read"
-    And user "Carol" has accepted share "/TMP" offered by user "Brian"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,create,update,read |
     Then the OCS status code should be "<ocs_status_code>"
@@ -122,9 +110,7 @@ Feature: sharing
     And group "grp1" has been created
     And user "Carol" has been added to group "grp1"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,update,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "Shares/TMP" with group "grp1" with permissions "share,read"
-    And user "Carol" has accepted share "/TMP" offered by user "Brian"
     When user "Alice" updates the last share using the sharing API with
       | permissions | share,create,update,read |
     Then the OCS status code should be "<ocs_status_code>"
@@ -139,9 +125,7 @@ Feature: sharing
   Scenario Outline: after losing share permissions user can still delete a previously reshared share
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian" with permissions "share,create,update,read"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "Shares/TMP" with user "Carol" with permissions "share,create,update,read"
-    And user "Carol" has accepted share "/TMP" offered by user "Brian"
     And user "Alice" has updated the last share of "Alice" with
       | permissions | create,update,read |
     When user "Brian" deletes the last share using the sharing API

tests/acceptance/features/coreApiShareReshareToShares3/reShareWithExpiryDate.feature

@@ -16,7 +16,6 @@ Feature: resharing a resource with an expiration date
   Scenario Outline: user should be able to set expiration while resharing a file with user
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" creates a share using the sharing API with settings
       | path        | /Shares/textfile0.txt |
       | shareType   | user                  |
@@ -25,7 +24,6 @@ Feature: resharing a resource with an expiration date
       | expireDate  | +3 days               |
     Then the HTTP status code should be "200"
     And the OCS status code should be "<ocs_status_code>"
-    And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
     And the information of the last share of user "Brian" should include
       | expiration | +3 days |
     And the response when user "Carol" gets the info of the last share should include
@@ -41,7 +39,6 @@ Feature: resharing a resource with an expiration date
     And group "grp1" has been created
     And user "Carol" has been added to group "grp1"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" creates a share using the sharing API with settings
       | path        | /Shares/textfile0.txt |
       | shareType   | group                 |
@@ -50,7 +47,6 @@ Feature: resharing a resource with an expiration date
       | expireDate  | +3 days               |
     Then the HTTP status code should be "200"
     And the OCS status code should be "<ocs_status_code>"
-    And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
     And the information of the last share of user "Brian" should include
       | expiration | +3 days |
     And the response when user "Carol" gets the info of the last share should include
@@ -64,7 +60,6 @@ Feature: resharing a resource with an expiration date
   Scenario Outline: resharing using the sharing API with default expire date set but not enforced
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian" with permissions "read,update,share"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" creates a share using the sharing API with settings
       | path        | /Shares/textfile0.txt |
       | shareType   | user                  |
@@ -72,7 +67,6 @@ Feature: resharing a resource with an expiration date
       | shareWith   | Carol                 |
     Then the HTTP status code should be "200"
     And the OCS status code should be "<ocs_status_code>"
-    And user "Carol" should be able to accept pending share "/textfile0.txt" offered by user "Brian"
     And the information of the last share of user "Brian" should include
       | expiration |  |
     And the response when user "Carol" gets the info of the last share should include

tests/acceptance/features/coreApiShareUpdateToShares/updateShare.feature

@@ -16,9 +16,7 @@ Feature: sharing
       | Carol    |
     And user "Alice" has created folder "/TMP"
     And user "Alice" has shared folder "TMP" with user "Brian"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     And user "Brian" has shared folder "/Shares/TMP" with user "Carol"
-    And user "Carol" has accepted share "/TMP" offered by user "Brian"
     When user "Brian" updates the last share using the sharing API with
       | permissions | read |
     Then the OCS status code should be "<ocs_status_code>"
@@ -38,7 +36,6 @@ Feature: sharing
     And user "Brian" has been added to group "grp1"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with group "grp1"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Brian" has moved file "/Shares/textfile0.txt" to "/Shares/textfile_new.txt"
     When user "Alice" updates the last share using the sharing API with
       | permissions | read |
@@ -84,7 +81,6 @@ Feature: sharing
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | <permissions> |
     Then the OCS status code should be "400"
@@ -108,7 +104,6 @@ Feature: sharing
     And user "Brian" has been added to group "grp1"
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with group "grp1"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | <permissions> |
     Then the OCS status code should be "400"
@@ -134,9 +129,7 @@ Feature: sharing
     And user "Alice" has created folder "/folder1/folder2"
     And user "Brian" has created folder "/moved-out"
     And user "Alice" has shared folder "/folder1" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/folder1" offered by user "Alice"
     And user "Brian" has shared folder "/Shares/folder1/folder2" with user "Carol" with permissions "all"
-    And user "Carol" has accepted share "/folder2" offered by user "Brian"
     When user "Brian" moves folder "/Shares/folder1/folder2" to "/moved-out/folder2" using the WebDAV API
     Then the HTTP status code should be "201"
     And the response when user "Brian" gets the info of the last share should include
@@ -166,9 +159,7 @@ Feature: sharing
     And user "Alice" has created folder "/Alice-folder/folder2"
     And user "Carol" has created folder "/Carol-folder"
     And user "Alice" has shared folder "/Alice-folder" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/Alice-folder" offered by user "Alice"
     And user "Carol" has shared folder "/Carol-folder" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/Carol-folder" offered by user "Carol"
     When user "Brian" moves folder "/Shares/Alice-folder/folder2" to "/Shares/Carol-folder/folder2" using the WebDAV API
     Then the HTTP status code should be "201"
     And the response when user "Carol" gets the info of the last share should include
@@ -245,7 +236,6 @@ Feature: sharing
     And user "Carol" has been added to group "grp1"
     And user "Carol" has created folder "/FOLDER"
     And user "Carol" has shared folder "/FOLDER" with group "grp1"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Carol"
     And user "Carol" has updated the last share with
       | permissions | read |
     When user "Carol" updates the last share using the sharing API with
@@ -268,7 +258,6 @@ Feature: sharing
       | shareType   | user   |
       | permissions | create |
       | shareWith   | Brian  |
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Brian" has uploaded file with content "some content" to "/Shares/FOLDER/textFile.txt"
     When user "Alice" deletes file "/FOLDER/textFile.txt" using the WebDAV API
     Then the HTTP status code should be "204"

tests/acceptance/features/coreApiShareUpdateToShares/updateShareGroupAndUserWithSameName.feature

@@ -20,8 +20,6 @@ Feature: updating shares to users and groups that have the same name
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with group "Brian"
     And user "Alice" has shared folder "/TMP" with user "Brian"
-    And user "Carol" has accepted share "/TMP" offered by user "Alice"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | read |
     Then the HTTP status code should be "200"
@@ -40,8 +38,6 @@ Feature: updating shares to users and groups that have the same name
     Given using OCS API version "<ocs_api_version>"
     And user "Alice" has shared folder "/TMP" with user "Brian"
     And user "Alice" has shared folder "/TMP" with group "Brian"
-    And user "Carol" has accepted share "/TMP" offered by user "Alice"
-    And user "Brian" has accepted share "/TMP" offered by user "Alice"
     When user "Alice" updates the last share using the sharing API with
       | permissions | read |
     Then the HTTP status code should be "200"

tests/acceptance/features/coreApiTrashbin/trashbinSharingToShares.feature

@@ -14,7 +14,6 @@ Feature: using trashbin together with sharing
     And user "Alice" has created folder "/shared"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
     And user "Alice" has shared folder "/shared" with user "Brian"
-    And user "Brian" has accepted share "/shared" offered by user "Alice"
     And user "Brian" has moved folder "/Shares/shared" to "/Shares/renamed_shared"
     When user "Brian" deletes folder "/Shares/renamed_shared" using the WebDAV API
     Then the HTTP status code should be "204"
@@ -35,7 +34,6 @@ Feature: using trashbin together with sharing
     And user "Alice" has created folder "/shared"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
     And user "Alice" has shared folder "/shared" with user "Brian"
-    And user "Brian" has accepted share "/shared" offered by user "Alice"
     And user "Brian" has moved file "/Shares/shared" to "/Shares/renamed_shared"
     When user "Brian" deletes file "/Shares/renamed_shared/shared_file.txt" using the WebDAV API
     Then the HTTP status code should be "204"
@@ -61,8 +59,6 @@ Feature: using trashbin together with sharing
     And user "Alice" has created folder "/shared"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
     And user "Alice" has shared folder "/shared" with group "grp1"
-    And user "Brian" has accepted share "/Shares/shared" offered by user "Alice"
-    And user "Carol" has accepted share "/Shares/shared" offered by user "Alice"
     When user "Brian" deletes file "/Shares/shared/shared_file.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And as "Brian" the file with original path "/Shares/shared/shared_file.txt" should exist in the trashbin
@@ -88,8 +84,6 @@ Feature: using trashbin together with sharing
     And user "Alice" has created folder "/shared"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
     And user "Alice" has shared folder "/shared" with group "grp1"
-    And user "Brian" has accepted share "/Shares/shared" offered by user "Alice"
-    And user "Carol" has accepted share "/Shares/shared" offered by user "Alice"
     When user "Alice" deletes file "/shared/shared_file.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And as "Alice" the file with original path "/shared/shared_file.txt" should exist in the trashbin
@@ -116,8 +110,6 @@ Feature: using trashbin together with sharing
     And user "Alice" has created folder "/shared/sub"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/sub/shared_file.txt"
     And user "Alice" has shared folder "/shared" with group "grp1"
-    And user "Brian" has accepted share "/Shares/shared" offered by user "Alice"
-    And user "Carol" has accepted share "/Shares/shared" offered by user "Alice"
     When user "Brian" deletes file "/Shares/shared/sub/shared_file.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And as "Brian" the file with original path "/Shares/shared/sub/shared_file.txt" should exist in the trashbin
@@ -144,8 +136,6 @@ Feature: using trashbin together with sharing
     And user "Alice" has created folder "/shared/sub"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/sub/shared_file.txt"
     And user "Alice" has shared folder "/shared" with group "grp1"
-    And user "Brian" has accepted share "/Shares/shared" offered by user "Alice"
-    And user "Carol" has accepted share "/Shares/shared" offered by user "Alice"
     When user "Alice" deletes file "/shared/sub/shared_file.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And as "Alice" the file with original path "/shared/sub/shared_file.txt" should exist in the trashbin
@@ -167,7 +157,6 @@ Feature: using trashbin together with sharing
     And user "Alice" has created folder "/shared"
     And user "Alice" has moved file "/textfile0.txt" to "/shared/shared_file.txt"
     And user "Alice" has shared folder "/shared" with user "Brian"
-    And user "Brian" has accepted share "/shared" offered by user "Alice"
     And user "Brian" has moved folder "/Shares/shared" to "/Shares/renamed_shared"
     And user "Brian" has deleted file "/Shares/renamed_shared/shared_file.txt"
     When user "Brian" restores the file with original path "/Shares/renamed_shared/shared_file.txt" using the trashbin API
@@ -194,7 +183,6 @@ Feature: using trashbin together with sharing
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Brian" has created folder "shareFolderParent"
     And user "Brian" has shared folder "shareFolderParent" with user "Alice" with permissions "read"
-    And user "Alice" has accepted share "/shareFolderParent" offered by user "Brian"
     And as "Alice" folder "/Shares/shareFolderParent" should exist
     And user "Alice" has deleted file "/textfile0.txt"
     When user "Alice" restores the file with original path "/textfile0.txt" to "/Shares/shareFolderParent/textfile0.txt" using the trashbin API
@@ -218,7 +206,6 @@ Feature: using trashbin together with sharing
     And user "Brian" has created folder "shareFolderParent"
     And user "Brian" has created folder "shareFolderParent/shareFolderChild"
     And user "Brian" has shared folder "shareFolderParent" with user "Alice" with permissions "read"
-    And user "Alice" has accepted share "/shareFolderParent" offered by user "Brian"
     And as "Alice" folder "/Shares/shareFolderParent/shareFolderChild" should exist
     And user "Alice" has deleted file "/textfile0.txt"
     When user "Alice" restores the file with original path "/textfile0.txt" to "/Shares/shareFolderParent/shareFolderChild/textfile0.txt" using the trashbin API

tests/acceptance/features/coreApiVersions/fileVersionAuthor.feature

@@ -16,11 +16,8 @@ Feature: file versions remember the author of each version
     Given user "David" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/test"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     And user "Alice" has shared folder "/test" with user "Carol" with permissions "all"
-    And user "Carol" has accepted share "/test" offered by user "Alice"
     And user "Alice" has shared folder "/test" with user "David" with permissions "all"
-    And user "David" has accepted share "/test" offered by user "Alice"
     And user "Alice" has uploaded file with content "uploaded content alice" to "/test/textfile0.txt"
     And user "Brian" has uploaded file with content "uploaded content brian" to "/Shares/test/textfile0.txt"
     And user "Carol" has uploaded file with content "uploaded content carol" to "/Shares/test/textfile0.txt"
@@ -50,8 +47,6 @@ Feature: file versions remember the author of each version
     And user "Brian" has been added to group "grp1"
     And user "Carol" has been added to group "grp1"
     And user "Alice" has shared folder "/test" with group "grp1"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
-    And user "Carol" has accepted share "/test" offered by user "Alice"
     And user "Alice" has uploaded file with content "uploaded content alice" to "/test/textfile0.txt"
     And user "Brian" has uploaded file with content "uploaded content brian" to "/Shares/test/textfile0.txt"
     And user "Carol" has uploaded file with content "uploaded content carol" to "/Shares/test/textfile0.txt"
@@ -77,8 +72,6 @@ Feature: file versions remember the author of each version
     And user "Carol" has been added to group "grp1"
     And user "Alice" has uploaded file with content "uploaded content alice" to "/textfile0.txt"
     And user "Alice" has shared file "/textfile0.txt" with group "grp1"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
-    And user "Carol" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Brian" has uploaded file with content "uploaded content brian" to "/Shares/textfile0.txt"
     And user "Carol" has uploaded file with content "uploaded content carol" to "/Shares/textfile0.txt"
     When user "Alice" gets the number of versions of file "textfile0.txt"
@@ -103,8 +96,6 @@ Feature: file versions remember the author of each version
     And user "Brian" has been added to group "grp1"
     And user "Carol" has been added to group "grp1"
     And user "Alice" has shared folder "/test" with group "grp1"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
-    And user "Carol" has accepted share "/test" offered by user "Alice"
     And user "Alice" has uploaded file with content "uploaded content alice" to "/test/textfile0.txt"
     And user "Brian" has uploaded file with content "uploaded content brian" to "/Shares/test/textfile0.txt"
     And user "Carol" has uploaded file with content "uploaded content carol" to "/Shares/test/textfile0.txt"
@@ -136,8 +127,6 @@ Feature: file versions remember the author of each version
     And user "Carol" has been added to group "grp1"
     And user "Alice" has uploaded file with content "uploaded content alice" to "/exist.txt"
     And user "Alice" has shared file "/exist.txt" with group "grp1"
-    And user "Brian" has accepted share "/exist.txt" offered by user "Alice"
-    And user "Carol" has accepted share "/exist.txt" offered by user "Alice"
     And user "Brian" has uploaded file with content "uploaded content brian" to "/Shares/exist.txt"
     And user "Carol" has uploaded file with content "uploaded content carol" to "/Shares/exist.txt"
     And user "Alice" has moved file "/exist.txt" to "/textfile0.txt"
@@ -163,8 +152,6 @@ Feature: file versions remember the author of each version
     And user "Carol" has been added to group "grp1"
     And user "Alice" has uploaded file with content "uploaded content alice" to "/exist.txt"
     And user "Alice" has shared file "/exist.txt" with group "grp1"
-    And user "Brian" has accepted share "/exist.txt" offered by user "Alice"
-    And user "Carol" has accepted share "/exist.txt" offered by user "Alice"
     And user "Brian" has uploaded file with content "uploaded content brian" to "/Shares/exist.txt"
     And user "Carol" has uploaded file with content "uploaded content carol" to "/Shares/exist.txt"
     And user "Brian" has moved file "/Shares/exist.txt" to "/Shares/textfile0.txt"
@@ -194,16 +181,12 @@ Feature: file versions remember the author of each version
     And user "Brian" has been added to group "grp1"
     And user "Carol" has been added to group "grp1"
     And user "Alice" has shared folder "/test" with group "grp1"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
-    And user "Carol" has accepted share "/test" offered by user "Alice"
     And user "Alice" has uploaded file with content "uploaded content alice" to "/test/textfile0.txt"
     And user "Brian" has uploaded file with content "uploaded content brian" to "/Shares/test/textfile0.txt"
     And user "Carol" has uploaded file with content "uploaded content carol" to "/Shares/test/textfile0.txt"
     And user "Alice" has deleted the last share
     And user "Alice" has uploaded file with content "uploaded content alice after unshared folder" to "/test/textfile0.txt"
     And user "Alice" has shared folder "/test" with group "grp1"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
-    And user "Carol" has accepted share "/test" offered by user "Alice"
     When user "Alice" gets the number of versions of file "/test/textfile0.txt"
     Then the HTTP status code should be "207"
     And the number of versions should be "3"
@@ -228,20 +211,14 @@ Feature: file versions remember the author of each version
     And user "Brian" has uploaded file with content "duplicate brian" to "/test/textfile0.txt"
     And user "Brian" has uploaded file with content "overwrite brian" to "/test/textfile0.txt"
     And user "Brian" has shared folder "/test" with user "Carol" with permissions "all"
-    And user "Carol" has accepted share "/test" offered by user "Brian"
     And user "Brian" has shared folder "/test" with user "David" with permissions "all"
-    And user "David" has accepted share "/test" offered by user "Brian"
     And user "Carol" has created folder "/test"
     And user "Carol" has uploaded file with content "duplicate carol" to "/test/textfile0.txt"
     And user "Carol" has shared folder "/test" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/test" offered by user "Carol"
     And user "Alice" has created folder "/test"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     And user "Alice" has shared folder "/test" with user "Carol" with permissions "all"
-    And user "Carol" has accepted share "/test" offered by user "Alice"
     And user "Alice" has shared folder "/test" with user "David" with permissions "all"
-    And user "David" has accepted share "/test" offered by user "Alice"
     And user "Alice" has uploaded file with content "uploaded content alice" to "/test/textfile0.txt"
     And user "Brian" has uploaded file with content "uploaded content brian" to "/Shares/test (1)/textfile0.txt"
     And user "Carol" has uploaded file with content "uploaded content carol" to "/Shares/test (1)/textfile0.txt"
@@ -279,19 +256,13 @@ Feature: file versions remember the author of each version
     And user "Brian" has uploaded file with content "duplicate brian" to "/textfile0.txt"
     And user "Brian" has uploaded file with content "overwrite brian" to "/textfile0.txt"
     And user "Brian" has shared file "/textfile0.txt" with user "Carol"
-    And user "Carol" has accepted share "/textfile0.txt" offered by user "Brian"
     And user "Brian" has shared file "/textfile0.txt" with user "David"
-    And user "David" has accepted share "/textfile0.txt" offered by user "Brian"
     And user "Carol" has uploaded file with content "duplicate carol" to "/textfile0.txt"
     And user "Carol" has shared file "/textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Carol"
     And user "Alice" has uploaded file with content "uploaded content alice" to "/textfile0.txt"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Alice" has shared file "/textfile0.txt" with user "Carol"
-    And user "Carol" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Alice" has shared file "/textfile0.txt" with user "David"
-    And user "David" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Brian" has uploaded file with content "uploaded content brian" to "/Shares/textfile0 (1).txt"
     And user "Carol" has uploaded file with content "uploaded content carol" to "/Shares/textfile0 (1).txt"
     And user "David" has uploaded file with content "uploaded content david" to "/Shares/textfile0 (1).txt"
@@ -326,9 +297,7 @@ Feature: file versions remember the author of each version
   Scenario: enable file versioning and check the version author after restoring a version of a file inside a folder
     Given user "Alice" has created folder "/test"
     And user "Alice" has shared folder "/test" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/test" offered by user "Alice"
     And user "Alice" has shared folder "/test" with user "Carol" with permissions "all"
-    And user "Carol" has accepted share "/test" offered by user "Alice"
     And user "Alice" has uploaded file with content "uploaded content alice" to "/test/textfile0.txt"
     And user "Brian" has uploaded file with content "uploaded content brian" to "/Shares/test/textfile0.txt"
     And user "Carol" has uploaded file with content "uploaded content carol" to "/Shares/test/textfile0.txt"
@@ -347,9 +316,7 @@ Feature: file versions remember the author of each version
   Scenario: enable file versioning and check the version author after restoring a version of a file
     Given user "Alice" has uploaded file with content "uploaded content alice" to "/textfile0.txt"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Alice" has shared file "/textfile0.txt" with user "Carol"
-    And user "Carol" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Brian" has uploaded file with content "uploaded content brian" to "/Shares/textfile0.txt"
     And user "Carol" has uploaded file with content "uploaded content carol" to "/Shares/textfile0.txt"
     When user "Brian" restores version index "1" of file "/Shares/textfile0.txt" using the WebDAV API

tests/acceptance/features/coreApiVersions/fileVersions.feature

@@ -275,7 +275,6 @@ Feature: dav-versions
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file with content "First content" to "sharefile.txt"
     And user "Alice" has shared file "sharefile.txt" with user "Brian"
-    And user "Brian" has accepted share "/sharefile.txt" offered by user "Alice"
     When user "Brian" uploads file with content "Second content" to "/Shares/sharefile.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And the version folder of file "/sharefile.txt" for user "Alice" should contain "1" element
@@ -287,7 +286,6 @@ Feature: dav-versions
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file with content "First content" to "sharefile.txt"
     And user "Alice" has shared file "sharefile.txt" with user "Brian"
-    And user "Brian" has accepted share "/sharefile.txt" offered by user "Alice"
     And user "Brian" has uploaded file with content "Second content" to "/Shares/sharefile.txt"
     When user "Alice" restores version index "1" of file "/sharefile.txt" using the WebDAV API
     Then the HTTP status code should be "204"
@@ -299,7 +297,6 @@ Feature: dav-versions
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/sharingfolder"
     And user "Alice" has shared folder "/sharingfolder" with user "Brian"
-    And user "Brian" has accepted share "/sharingfolder" offered by user "Alice"
     And user "Alice" has uploaded file with content "First content" to "/sharingfolder/sharefile.txt"
     And user "Brian" has uploaded file with content "Second content" to "/Shares/sharingfolder/sharefile.txt"
     When user "Alice" restores version index "1" of file "/sharingfolder/sharefile.txt" using the WebDAV API
@@ -312,7 +309,6 @@ Feature: dav-versions
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/sharingfolder"
     And user "Alice" has shared folder "/sharingfolder" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/sharingfolder" offered by user "Alice"
     And user "Alice" has uploaded file with content "First content" to "/sharingfolder/sharefile.txt"
     When user "Brian" has uploaded file with content "Second content" to "/Shares/sharingfolder/sharefile.txt"
     And user "Brian" gets the number of versions of file "/Shares/sharingfolder/sharefile.txt"
@@ -325,7 +321,6 @@ Feature: dav-versions
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/sharingfolder"
     And user "Alice" has shared folder "/sharingfolder" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/sharingfolder" offered by user "Alice"
     And user "Brian" has uploaded file with content "First content" to "/Shares/sharingfolder/sharefile.txt"
     And user "Alice" has uploaded file with content "Second content" to "/sharingfolder/sharefile.txt"
     When user "Alice" restores version index "1" of file "/sharingfolder/sharefile.txt" using the WebDAV API
@@ -338,7 +333,6 @@ Feature: dav-versions
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/sharingfolder"
     And user "Alice" has shared folder "/sharingfolder" with user "Brian" with permissions "all"
-    And user "Brian" has accepted share "/sharingfolder" offered by user "Alice"
     And user "Brian" has uploaded file with content "old content" to "/Shares/sharingfolder/sharefile.txt"
     And user "Brian" has uploaded file with content "new content" to "/Shares/sharingfolder/sharefile.txt"
     When user "Alice" restores version index "1" of file "/sharingfolder/sharefile.txt" using the WebDAV API
@@ -355,8 +349,6 @@ Feature: dav-versions
     And user "Carol" has been added to group "grp1"
     And user "Alice" has created folder "/sharingfolder"
     And user "Alice" has shared folder "/sharingfolder" with group "grp1"
-    And user "Brian" has accepted share "/sharingfolder" offered by user "Alice"
-    And user "Carol" has accepted share "/sharingfolder" offered by user "Alice"
     And user "Alice" has uploaded file with content "First content" to "/sharingfolder/sharefile.txt"
     And user "Brian" has uploaded file with content "Second content" to "/Shares/sharingfolder/sharefile.txt"
     And user "Carol" has uploaded file with content "Third content" to "/Shares/sharingfolder/sharefile.txt"
@@ -376,7 +368,6 @@ Feature: dav-versions
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     And user "Brian" has uploaded file with content "test data 1" to "/testfile.txt"
     And user "Brian" has uploaded file with content "test data 2" to "/testfile.txt"
     And user "Brian" has uploaded file with content "test data 3" to "/testfile.txt"
@@ -404,7 +395,6 @@ Feature: dav-versions
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Brian" moves file "/testshare/testfile.txt" to "/testfile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/testfile.txt" for user "Brian" should be "test data 3"
@@ -422,7 +412,6 @@ Feature: dav-versions
     And user "Alice" has uploaded file with content "textfile0" to "textfile0.txt"
     And user "Alice" has uploaded file with content "textfile1" to "textfile1.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" tries to get versions of file "textfile1.txt" from "Alice"
     Then the HTTP status code should be "404"
     And the value of the item "//s:exception" in the response about user "Alice" should be "Sabre\DAV\Exception\NotFound"
@@ -435,7 +424,6 @@ Feature: dav-versions
     And user "Alice" has uploaded file with content "version 2" to "textfile0.txt"
     And user "Alice" has uploaded file with content "version 3" to "textfile0.txt"
     And user "Alice" has shared file "textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     When user "Brian" tries to get versions of file "textfile0.txt" from "Alice"
     Then the HTTP status code should be "403"
 

tests/acceptance/features/coreApiWebdavEtagPropagation1/deleteFileFolder.feature

@@ -90,7 +90,6 @@ Feature: propagation of etags when deleting a file or folder
     And user "Alice" has created folder "/upload/sub"
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/sub/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Alice" has stored etag of element "/upload/sub"
@@ -121,7 +120,6 @@ Feature: propagation of etags when deleting a file or folder
     And user "Alice" has created folder "/upload/sub"
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/sub/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Alice" has stored etag of element "/upload/sub"
@@ -152,7 +150,6 @@ Feature: propagation of etags when deleting a file or folder
     And user "Alice" has created folder "/upload/sub"
     And user "Alice" has created folder "/upload/sub/toDelete"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Alice" has stored etag of element "/upload/sub"
@@ -183,7 +180,6 @@ Feature: propagation of etags when deleting a file or folder
     And user "Alice" has created folder "/upload/sub"
     And user "Alice" has created folder "/upload/sub/toDelete"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Alice" has stored etag of element "/upload/sub"

tests/acceptance/features/coreApiWebdavEtagPropagation1/moveFileFolder.feature

@@ -163,7 +163,6 @@ Feature: propagation of etags when moving files or folders
     And user "Alice" has created folder "/upload"
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Brian" has stored etag of element "/"
@@ -190,7 +189,6 @@ Feature: propagation of etags when moving files or folders
     And user "Alice" has created folder "/upload"
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Brian" has stored etag of element "/"
@@ -218,9 +216,7 @@ Feature: propagation of etags when moving files or folders
     And user "Alice" has created folder "/dst"
     And user "Alice" has uploaded file with content "uploaded content" to "/src/file.txt"
     And user "Alice" has shared folder "/src" with user "Brian"
-    And user "Brian" has accepted share "/src" offered by user "Alice"
     And user "Alice" has shared folder "/dst" with user "Brian"
-    And user "Brian" has accepted share "/dst" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/src"
     And user "Alice" has stored etag of element "/dst"
@@ -252,9 +248,7 @@ Feature: propagation of etags when moving files or folders
     And user "Alice" has created folder "/dst"
     And user "Alice" has uploaded file with content "uploaded content" to "/src/file.txt"
     And user "Alice" has shared folder "/src" with user "Brian"
-    And user "Brian" has accepted share "/src" offered by user "Alice"
     And user "Alice" has shared folder "/dst" with user "Brian"
-    And user "Brian" has accepted share "/dst" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/src"
     And user "Alice" has stored etag of element "/dst"
@@ -286,9 +280,7 @@ Feature: propagation of etags when moving files or folders
     And user "Alice" has created folder "/dst"
     And user "Alice" has created folder "/src/toMove"
     And user "Alice" has shared folder "/src" with user "Brian"
-    And user "Brian" has accepted share "/src" offered by user "Alice"
     And user "Alice" has shared folder "/dst" with user "Brian"
-    And user "Brian" has accepted share "/dst" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/src"
     And user "Alice" has stored etag of element "/dst"
@@ -320,9 +312,7 @@ Feature: propagation of etags when moving files or folders
     And user "Alice" has created folder "/dst"
     And user "Alice" has created folder "/src/toMove"
     And user "Alice" has shared folder "/src" with user "Brian"
-    And user "Brian" has accepted share "/src" offered by user "Alice"
     And user "Alice" has shared folder "/dst" with user "Brian"
-    And user "Brian" has accepted share "/dst" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/src"
     And user "Alice" has stored etag of element "/dst"

tests/acceptance/features/coreApiWebdavEtagPropagation2/copyFileFolder.feature

@@ -160,7 +160,6 @@ Feature: propagation of etags when copying files or folders
     And user "Alice" has created folder "/upload"
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Alice" has stored etag of element "/upload/file.txt"
@@ -197,7 +196,6 @@ Feature: propagation of etags when copying files or folders
     And user "Alice" has created folder "/upload"
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Alice" has stored etag of element "/upload/file.txt"

tests/acceptance/features/coreApiWebdavEtagPropagation2/createFolder.feature

@@ -59,7 +59,6 @@ Feature: propagation of etags when creating folders
     And using <dav-path-version> DAV path
     And user "Alice" has created folder "/folder"
     And user "Alice" has shared folder "/folder" with user "Brian"
-    And user "Brian" has accepted share "/folder" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/folder"
     And user "Brian" has stored etag of element "/"
@@ -85,7 +84,6 @@ Feature: propagation of etags when creating folders
     And using <dav-path-version> DAV path
     And user "Alice" has created folder "/folder"
     And user "Alice" has shared folder "/folder" with user "Brian"
-    And user "Brian" has accepted share "/folder" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/folder"
     And user "Brian" has stored etag of element "/"

tests/acceptance/features/coreApiWebdavEtagPropagation2/upload.feature

@@ -57,7 +57,6 @@ Feature: propagation of etags when uploading data
     Given user "Brian" has been created with default attributes and without skeleton files
     And using <dav-path-version> DAV path
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Brian" has stored etag of element "/"
@@ -82,7 +81,6 @@ Feature: propagation of etags when uploading data
     Given user "Brian" has been created with default attributes and without skeleton files
     And using <dav-path-version> DAV path
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Brian" has stored etag of element "/"
@@ -108,7 +106,6 @@ Feature: propagation of etags when uploading data
     And using <dav-path-version> DAV path
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Brian" has stored etag of element "/"
@@ -134,7 +131,6 @@ Feature: propagation of etags when uploading data
     And using <dav-path-version> DAV path
     And user "Alice" has uploaded file with content "uploaded content" to "/upload/file.txt"
     And user "Alice" has shared folder "/upload" with user "Brian"
-    And user "Brian" has accepted share "/upload" offered by user "Alice"
     And user "Alice" has stored etag of element "/"
     And user "Alice" has stored etag of element "/upload"
     And user "Brian" has stored etag of element "/"

tests/acceptance/features/coreApiWebdavLocks/requestsWithToken.feature

@@ -14,7 +14,6 @@ Feature: actions on a locked item are possible if the token is sent with the req
     And user "Alice" has uploaded file with content "some data" to "textfile0.txt"
     And user "Brian" has uploaded file with content "some data" to "textfile0.txt"
     And user "Alice" has shared file "/textfile0.txt" with user "Brian"
-    And user "Brian" has accepted share "/textfile0.txt" offered by user "Alice"
     And user "Alice" has locked file "textfile0.txt" setting the following properties
       | lockscope | shared |
     And user "Brian" has locked file "Shares/textfile0.txt" setting the following properties

tests/acceptance/features/coreApiWebdavLocks2/independentLocksShareToShares.feature

@@ -18,8 +18,6 @@ Feature: independent locks - make sure all locks are independent and don't inter
     And user "Brian" has uploaded file "filesForUpload/textfile.txt" to "/FromBrian/textfile0.txt"
     And user "Alice" has shared folder "FromAlice" with user "Carol"
     And user "Brian" has shared folder "FromBrian" with user "Carol"
-    And user "Carol" has accepted share "/FromAlice" offered by user "Alice"
-    And user "Carol" has accepted share "/FromBrian" offered by user "Brian"
     When user "Carol" locks file "/Shares/FromBrian/textfile0.txt" using the WebDAV API setting the following properties
       | lockscope | <lock-scope> |
     Then the HTTP status code should be "200"
@@ -47,8 +45,6 @@ Feature: independent locks - make sure all locks are independent and don't inter
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/notlocked/textfile0.txt"
     And user "Alice" has shared folder "locked" with user "Brian"
     And user "Alice" has shared folder "notlocked" with user "Brian"
-    And user "Brian" has accepted share "/locked" offered by user "Alice"
-    And user "Brian" has accepted share "/notlocked" offered by user "Alice"
     When user "Brian" locks file "/Shares/locked/textfile0.txt" using the WebDAV API setting the following properties
       | lockscope | <lock-scope> |
     Then the HTTP status code should be "200"

tests/acceptance/features/coreApiWebdavLocksUnlock/unlockSharingToShares.feature

@@ -18,7 +18,6 @@ Feature: UNLOCK locked items (sharing)
     And user "Alice" has locked file "PARENT/parent.txt" setting the following properties
       | lockscope | <lock-scope> |
     And user "Alice" has shared file "PARENT/parent.txt" with user "Brian"
-    And user "Brian" has accepted share "/parent.txt" offered by user "Alice"
     When user "Brian" unlocks file "Shares/parent.txt" with the last created lock of file "PARENT/parent.txt" of user "Alice" using the WebDAV API
     Then the HTTP status code should be "403"
     And 1 locks should be reported for file "PARENT/parent.txt" of user "Alice" by the WebDAV API
@@ -42,7 +41,6 @@ Feature: UNLOCK locked items (sharing)
     And user "Alice" has locked file "PARENT/parent.txt" setting the following properties
       | lockscope | <lock-scope> |
     And user "Alice" has shared folder "PARENT" with user "Brian"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     When user "Brian" unlocks file "Shares/PARENT/parent.txt" with the last created lock of file "PARENT/parent.txt" of user "Alice" using the WebDAV API
     Then the HTTP status code should be "403"
     And 1 locks should be reported for file "PARENT/parent.txt" of user "Alice" by the WebDAV API
@@ -64,7 +62,6 @@ Feature: UNLOCK locked items (sharing)
   Scenario Outline: sharee unlock a shared file
     Given using <dav-path-version> DAV path
     And user "Alice" has shared file "PARENT/parent.txt" with user "Brian"
-    And user "Brian" has accepted share "/parent.txt" offered by user "Alice"
     And user "Brian" has locked file "Shares/parent.txt" setting the following properties
       | lockscope | <lock-scope> |
     When user "Brian" unlocks the last created lock of file "Shares/parent.txt" using the WebDAV API
@@ -88,7 +85,6 @@ Feature: UNLOCK locked items (sharing)
   Scenario Outline: as owner unlocking a shared file locked by the receiver is not possible. To unlock use the receivers locktoken
     Given using <dav-path-version> DAV path
     And user "Alice" has shared file "PARENT/parent.txt" with user "Brian"
-    And user "Brian" has accepted share "/parent.txt" offered by user "Alice"
     And user "Brian" has locked file "Shares/parent.txt" setting the following properties
       | lockscope | <lock-scope> |
     When user "Alice" unlocks file "PARENT/parent.txt" with the last created lock of file "Shares/parent.txt" of user "Brian" using the WebDAV API
@@ -112,7 +108,6 @@ Feature: UNLOCK locked items (sharing)
   Scenario Outline: unlocking a file in a shared folder, which was locked by the sharee is not possible for the owner unless the receiver's locktoken is used
     Given using <dav-path-version> DAV path
     And user "Alice" has shared folder "PARENT" with user "Brian"
-    And user "Brian" has accepted share "/PARENT" offered by user "Alice"
     And user "Brian" has locked file "Shares/PARENT/parent.txt" setting the following properties
       | lockscope | <lock-scope> |
     When user "Alice" unlocks file "PARENT/parent.txt" with the last created lock of file "Shares/PARENT/parent.txt" of user "Brian" using the WebDAV API

tests/acceptance/features/coreApiWebdavMove2/moveShareOnOcis.feature

@@ -18,7 +18,6 @@ Feature: move (rename) file
       | permissions | change    |
       | shareWith   | Alice     |
     And user "<mover>" has uploaded file with content "test data" to "/testfile.txt"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "<mover>" moves file "/testfile.txt" to "<destination_folder>/testfile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/Shares/testshare/testfile.txt" for user "Alice" should be "test data"
@@ -42,7 +41,6 @@ Feature: move (rename) file
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Brian" moves file "/testshare/testfile.txt" to "/testfile.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/testfile.txt" for user "Brian" should be "test data"
@@ -64,7 +62,6 @@ Feature: move (rename) file
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" moves file "/Shares/testshare/testfile.txt" to "/testfile.txt" using the WebDAV API
     Then the HTTP status code should be "502"
     And as "Alice" file "/Shares/testshare/testfile.txt" should exist
@@ -86,7 +83,6 @@ Feature: move (rename) file
       | shareWith   | Alice     |
     And user "<mover>" has created folder "/testsubfolder"
     And user "<mover>" has uploaded file with content "test data" to "/testsubfolder/testfile.txt"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "<mover>" moves folder "/testsubfolder" to "<destination_folder>/testsubfolder" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/Shares/testshare/testsubfolder/testfile.txt" for user "Alice" should be "test data"
@@ -113,7 +109,6 @@ Feature: move (rename) file
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Brian" moves folder "/testshare/testsubfolder" to "/testsubfolder" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/testsubfolder/testfile.txt" for user "Brian" should be "test data"
@@ -138,7 +133,6 @@ Feature: move (rename) file
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" moves folder "/Shares/testshare/testsubfolder" to "/testsubfolder" using the WebDAV API
     Then the HTTP status code should be "502"
     And as "Alice" folder "/Shares/testshare/testsubfolder" should exist
@@ -159,7 +153,6 @@ Feature: move (rename) file
       | shareType   | user      |
       | permissions | read      |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" moves file "/textfile0.txt" to "/Shares/testshare/textfile0.txt" using the WebDAV API
     Then the HTTP status code should be "403"
     And user "Alice" should not be able to download file "/Shares/testshare/textfile0.txt"
@@ -181,7 +174,6 @@ Feature: move (rename) file
       | permissions | read      |
       | shareWith   | Alice     |
     And user "Brian" has copied file "/fileToCopy.txt" to "/testshare/overwritethis.txt"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" moves file "/textfile0.txt" to "/Shares/testshare/overwritethis.txt" using the WebDAV API
     Then the HTTP status code should be "403"
     And the content of file "/Shares/testshare/overwritethis.txt" for user "Alice" should be "Welcome to ownCloud"
@@ -200,8 +192,6 @@ Feature: move (rename) file
       | /folderB |
     And user "Alice" has shared folder "/folderA" with user "Brian"
     And user "Alice" has shared folder "/folderB" with user "Brian"
-    And user "Brian" has accepted share "/folderA" offered by user "Alice"
-    And user "Brian" has accepted share "/folderB" offered by user "Alice"
     And user "Brian" has created the following folders
       | path                    |
       | /Shares/folderA/ONE     |

tests/acceptance/features/coreApiWebdavPreviews/previews.feature

@@ -140,7 +140,6 @@ Feature: previews of files downloaded through the webdav API
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file "filesForUpload/<resource>" to "/<resource>"
     And user "Alice" has shared file "/<resource>" with user "Brian"
-    And user "Brian" has accepted share "/<resource>" offered by user "Alice"
     When user "Brian" downloads the preview of shared resource "/Shares/<resource>" with width "32" and height "32" using the WebDAV API
     Then the HTTP status code should be "200"
     And the downloaded image should be "32" pixels wide and "32" pixels high
@@ -214,8 +213,7 @@ Feature: previews of files downloaded through the webdav API
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file "filesForUpload/lorem.txt" to "/parent.txt"
     And user "Alice" has shared file "/parent.txt" with user "Brian"
-    And user "Brian" has accepted share "/parent.txt" offered by user "Alice"
-    And user "Brian" has downloaded the preview of shared resource "/Shares/parent.txt" with width "32" and height "32"
+    And user "Brian" has downloaded the preview of "/Shares/parent.txt" with width "32" and height "32"
     When user "Alice" uploads file with content "this is a file to upload" to "/parent.txt" using the WebDAV API
     Then the HTTP status code should be "204"
     And as user "Brian" the preview of shared resource "/Shares/parent.txt" with width "32" and height "32" should have been changed
@@ -247,7 +245,6 @@ Feature: previews of files downloaded through the webdav API
     And user "Alice" has created folder "FOLDER"
     And user "Alice" has uploaded file with content "file to upload" to "/FOLDER/lorem.txt"
     And user "Alice" has shared folder "FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Alice" has downloaded the preview of "/FOLDER/lorem.txt" with width "32" and height "32"
     And user "Brian" has downloaded the preview of shared resource "Shares/FOLDER/lorem.txt" with width "32" and height "32"
     When user "Alice" uploads file "filesForUpload/lorem.txt" to "/FOLDER/lorem.txt" using the WebDAV API
@@ -275,8 +272,6 @@ Feature: previews of files downloaded through the webdav API
     And user "Alice" has created folder "FOLDER"
     And user "Alice" has uploaded file with content "file to upload" to "/FOLDER/lorem.txt"
     And user "Alice" has shared folder "/FOLDER" with group "grp1"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
-    And user "Carol" has accepted share "/FOLDER" offered by user "Alice"
     And user "Alice" has downloaded the preview of "/FOLDER/lorem.txt" with width "32" and height "32"
     And user "Brian" has downloaded the preview of shared resource "Shares/FOLDER/lorem.txt" with width "32" and height "32"
     And user "Carol" has downloaded the preview of shared resource "Shares/FOLDER/lorem.txt" with width "32" and height "32"

tests/acceptance/features/coreApiWebdavProperties1/copyFile.feature

@@ -70,7 +70,6 @@ Feature: copy file
       | shareType   | user      |
       | permissions | read      |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies file "/textfile0.txt" to "/Shares/testshare/textfile0.txt" using the WebDAV API
     Then the HTTP status code should be "403"
     And user "Alice" should not be able to download file "/Shares/testshare/textfile0.txt"
@@ -90,7 +89,6 @@ Feature: copy file
       | shareType   | user      |
       | permissions | read      |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     And user "Brian" has copied file "textfile1.txt" to "/testshare/overwritethis.txt"
     When user "Alice" copies file "/textfile0.txt" to "/Shares/testshare/overwritethis.txt" using the WebDAV API
     Then the HTTP status code should be "403"
@@ -259,7 +257,6 @@ Feature: copy file
     And user "Brian" has created folder "/BRIAN-Folder"
     And user "Brian" has created folder "BRIAN-Folder/sample-folder"
     And user "Brian" has shared folder "BRIAN-Folder" with user "Alice"
-    And user "Alice" has accepted share "/BRIAN-Folder" offered by user "Brian"
     When user "Alice" copies file "/textfile1.txt" to "/Shares/BRIAN-Folder" using the WebDAV API
     Then the HTTP status code should be "204"
     And the content of file "/Shares/BRIAN-Folder" for user "Alice" should be "ownCloud test text file 1"
@@ -277,7 +274,6 @@ Feature: copy file
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Brian" has uploaded file with content "file to share" to "/sharedfile1.txt"
     And user "Brian" has shared file "/sharedfile1.txt" with user "Alice"
-    And user "Alice" has accepted share "/sharedfile1.txt" offered by user "Brian"
     And user "Alice" has created folder "FOLDER/sample-folder"
     When user "Alice" copies folder "/FOLDER" to "/Shares/sharedfile1.txt" using the WebDAV API
     Then the HTTP status code should be "204"
@@ -297,7 +293,6 @@ Feature: copy file
     And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder"
     And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder/third-level-folder"
     And user "Brian" has shared folder "BRIAN-FOLDER" with user "Alice"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "Sample-Folder-A"
     And user "Alice" has created folder "Sample-Folder-A/sample-folder-b"
     And user "Alice" has created folder "Sample-Folder-A/sample-folder-b/sample-folder-c"
@@ -320,7 +315,6 @@ Feature: copy file
     And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder"
     And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder/third-level-folder"
     And user "Brian" has shared folder "BRIAN-FOLDER" with user "Alice"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "Sample-Folder-A"
     And user "Alice" has created folder "Sample-Folder-A/sample-folder-b"
     And user "Alice" has uploaded file with content "sample file-c" to "Sample-Folder-A/sample-folder-b/textfile-c.txt"
@@ -344,7 +338,6 @@ Feature: copy file
     And user "Brian" has created folder "BRIAN-FOLDER"
     And user "Brian" has uploaded file with content "file at second level" to "BRIAN-FOLDER/second-level-file.txt"
     And user "Brian" has shared folder "BRIAN-FOLDER" with user "Alice"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "Sample-Folder-A"
     And user "Alice" has created folder "Sample-Folder-A/sample-folder-b"
     And user "Alice" has uploaded file with content "sample file-c" to "Sample-Folder-A/sample-folder-b/textfile-c.txt"
@@ -369,7 +362,6 @@ Feature: copy file
     And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder"
     And user "Brian" has uploaded file with content "file at third level" to "BRIAN-FOLDER/second-level-folder/third-level-file.txt"
     And user "Brian" has shared folder "BRIAN-FOLDER" with user "Alice"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "FOLDER/second-level-folder"
     And user "Alice" has created folder "FOLDER/second-level-folder/third-level-folder"
     When user "Alice" copies folder "FOLDER/second-level-folder" to "/Shares/BRIAN-FOLDER/second-level-folder/third-level-file.txt" using the WebDAV API
@@ -395,7 +387,6 @@ Feature: copy file
     And user "Brian" has created folder "/BRIAN-Folder"
     And user "Brian" has created folder "BRIAN-Folder/sample-folder"
     And user "Brian" has shared folder "BRIAN-Folder" with group "grp1" with permissions "15"
-    And user "Alice" has accepted share "/BRIAN-Folder" offered by user "Brian"
     When user "Alice" copies file "/textfile1.txt" to "/Shares/BRIAN-Folder" using the WebDAV API
     Then the HTTP status code should be "204"
     And the content of file "/Shares/BRIAN-Folder" for user "Alice" should be "ownCloud test text file 1"
@@ -421,7 +412,6 @@ Feature: copy file
     And user "Brian" has been added to group "grp1"
     And user "Brian" has uploaded file with content "file to share" to "/sharedfile1.txt"
     And user "Brian" has shared file "/sharedfile1.txt" with group "grp1"
-    And user "Alice" has accepted share "/sharedfile1.txt" offered by user "Brian"
     And user "Alice" has created folder "FOLDER/sample-folder"
     When user "Alice" copies folder "/FOLDER" to "/Shares/sharedfile1.txt" using the WebDAV API
     Then the HTTP status code should be "204"
@@ -449,7 +439,6 @@ Feature: copy file
     And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder"
     And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder/third-level-folder"
     And user "Brian" has shared folder "BRIAN-FOLDER" with group "grp1"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "Sample-Folder-A"
     And user "Alice" has created folder "Sample-Folder-A/sample-folder-b"
     And user "Alice" has created folder "Sample-Folder-A/sample-folder-b/sample-folder-c"
@@ -475,7 +464,6 @@ Feature: copy file
     And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder"
     And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder/third-level-folder"
     And user "Brian" has shared folder "BRIAN-FOLDER" with group "grp1"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "Sample-Folder-A"
     And user "Alice" has created folder "Sample-Folder-A/sample-folder-b"
     And user "Alice" has uploaded file with content "sample file-c" to "Sample-Folder-A/sample-folder-b/textfile-c.txt"
@@ -502,7 +490,6 @@ Feature: copy file
     And user "Brian" has created folder "BRIAN-FOLDER"
     And user "Brian" has uploaded file with content "file at second level" to "BRIAN-FOLDER/second-level-file.txt"
     And user "Brian" has shared folder "BRIAN-FOLDER" with group "grp1"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "Sample-Folder-A"
     And user "Alice" has created folder "Sample-Folder-A/sample-folder-b"
     And user "Alice" has uploaded file with content "sample file-c" to "Sample-Folder-A/sample-folder-b/textfile-c.txt"
@@ -530,7 +517,6 @@ Feature: copy file
     And user "Brian" has created folder "BRIAN-FOLDER/second-level-folder"
     And user "Brian" has uploaded file with content "file at third level" to "BRIAN-FOLDER/second-level-folder/third-level-file.txt"
     And user "Brian" has shared folder "BRIAN-FOLDER" with group "grp1"
-    And user "Alice" has accepted share "/BRIAN-FOLDER" offered by user "Brian"
     And user "Alice" has created folder "FOLDER/second-level-folder"
     And user "Alice" has created folder "FOLDER/second-level-folder/third-level-folder"
     When user "Alice" copies folder "FOLDER/second-level-folder" to "Shares/BRIAN-FOLDER/second-level-folder/third-level-file.txt" using the WebDAV API
@@ -626,7 +612,6 @@ Feature: copy file
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Alice" copies file "/textfile0.txt" to "/Shares/testshare/textfile0.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/Shares/testshare/textfile0.txt" for user "Alice" should be "ownCloud test text file 0"
@@ -647,7 +632,6 @@ Feature: copy file
       | permissions | change    |
       | shareWith   | Alice     |
     And user "Brian" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Brian" copies file "/textfile0.txt" to "/testshare/textfile0.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And the content of file "/Shares/testshare/textfile0.txt" for user "Alice" should be "ownCloud test text file 0"
@@ -667,7 +651,6 @@ Feature: copy file
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     And user "Alice" has uploaded file with content "ownCloud test text file inside share" to "/Shares/testshare/fileInsideShare.txt"
     When user "Alice" copies file "/Shares/testshare/fileInsideShare.txt" to "/fileInsideShare.txt" using the WebDAV API
     Then the HTTP status code should be "201"
@@ -690,7 +673,6 @@ Feature: copy file
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Alice     |
-    And user "Alice" has accepted share "/testshare" offered by user "Brian"
     When user "Brian" copies file "testshare/fileInsideShare.txt" to "/fileInsideShare.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" file "/fileInsideShare.txt" should exist
@@ -746,8 +728,6 @@ Feature: copy file
       | shareType   | user       |
       | permissions | change     |
       | shareWith   | Alice      |
-    And user "Alice" has accepted share "/testshare0" offered by user "Brian"
-    And user "Alice" has accepted share "/testshare1" offered by user "Carol"
     When user "Alice" copies file "/Shares/testshare0/testshare0.txt" to "/Shares/testshare1/testshare0.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Carol" file "testshare1/testshare0.txt" should exist
@@ -778,8 +758,6 @@ Feature: copy file
       | shareType   | user       |
       | permissions | change     |
       | shareWith   | Alice      |
-    And user "Alice" has accepted share "/testshare0" offered by user "Brian"
-    And user "Alice" has accepted share "/testshare1" offered by user "Carol"
     When user "Alice" copies file "/Shares/testshare0/folder_to_copy/" to "/Shares/testshare1/folder_to_copy/" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Carol" file "testshare1/folder_to_copy/testshare0.txt" should exist
@@ -802,13 +780,11 @@ Feature: copy file
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Brian     |
-    And user "Brian" has accepted share "/testshare" offered by user "Alice"
     And user "Alice" has created a share with settings
       | path        | testshare |
       | shareType   | user      |
       | permissions | change    |
       | shareWith   | Carol     |
-    And user "Carol" has accepted share "/testshare" offered by user "Alice"
     When user "Alice" copies file "/textfile0.txt" to "/testshare/textfile0.txt" using the WebDAV API
     Then the HTTP status code should be "201"
     And as "Brian" file "/Shares/testshare/textfile0.txt" should exist

tests/acceptance/features/coreApiWebdavProperties1/createFileFolderWhenSharesExist.feature

@@ -10,7 +10,6 @@ Feature: create file or folder named similar to Shares folder
       | Brian    |
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "read,update"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
 
 
   Scenario Outline: create a folder with a name similar to Shares

tests/acceptance/features/coreApiWebdavUploadTUS/uploadFileMtimeShares.feature

@@ -14,7 +14,6 @@ Feature: upload file
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" using the TUS protocol on the WebDAV API
     Then as "Alice" the mtime of the file "/toShare/file.txt" should be "Thu, 08 Aug 2012 04:18:13 GMT"
     And as "Brian" the mtime of the file "/Shares/toShare/file.txt" should be "Thu, 08 Aug 2012 04:18:13 GMT"
@@ -28,7 +27,6 @@ Feature: upload file
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     When user "Alice" uploads file "filesForUpload/textfile.txt" to "/toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" using the TUS protocol on the WebDAV API
     Then as "Alice" the mtime of the file "/toShare/file.txt" should be "Thu, 08 Aug 2012 04:18:13 GMT"
     And as "Brian" the mtime of the file "/Shares/toShare/file.txt" should be "Thu, 08 Aug 2012 04:18:13 GMT"
@@ -42,7 +40,6 @@ Feature: upload file
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     And user "Alice" has uploaded file with content "uploaded content" to "/toShare/file.txt"
     When user "Brian" uploads file "filesForUpload/textfile.txt" to "/Shares/toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" using the TUS protocol on the WebDAV API
     Then as "Alice" the mtime of the file "/toShare/file.txt" should be "Thu, 08 Aug 2012 04:18:13 GMT"
@@ -57,7 +54,6 @@ Feature: upload file
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/toShare"
     And user "Alice" has shared folder "/toShare" with user "Brian"
-    And user "Brian" has accepted share "/toShare" offered by user "Alice"
     And user "Brian" has uploaded file with content "uploaded content" to "/Shares/toShare/file.txt"
     When user "Alice" uploads file "filesForUpload/textfile.txt" to "/toShare/file.txt" with mtime "Thu, 08 Aug 2012 04:18:13 GMT" using the TUS protocol on the WebDAV API
     Then as "Alice" the mtime of the file "/toShare/file.txt" should be "Thu, 08 Aug 2012 04:18:13 GMT"

tests/acceptance/features/coreApiWebdavUploadTUS/uploadToNonExistingFolder.feature

@@ -40,7 +40,6 @@ Feature: upload file
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file with content "uploaded content" to "/Shares/FOLDER/nonExistentFolder/textfile.txt" using the TUS protocol on the WebDAV API
     Then as "Brian" folder "/Shares/FOLDER/nonExistentFolder" should not exist
     And as "Brian" file "/Shares/FOLDER/nonExistentFolder/textfile.txt" should not exist
@@ -55,7 +54,6 @@ Feature: upload file
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "read"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file with content "uploaded content" to "/Shares/FOLDER/nonExistentFolder/textfile.txt" using the TUS protocol on the WebDAV API
     Then as "Brian" folder "/Shares/FOLDER/nonExistentFolder" should not exist
     And as "Brian" file "/Shares/FOLDER/nonExistentFolder/textfile.txt" should not exist

tests/acceptance/features/coreApiWebdavUploadTUS/uploadToShare.feature

@@ -14,7 +14,6 @@ Feature: upload file to shared folder
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file with content "uploaded content" to "/Shares/FOLDER/textfile.txt" using the TUS protocol on the WebDAV API
     Then as "Alice" file "/FOLDER/textfile.txt" should exist
     And the content of file "/FOLDER/textfile.txt" for user "Alice" should be "uploaded content"
@@ -28,7 +27,6 @@ Feature: upload file to shared folder
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "change"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file with content "uploaded content" to "/Shares/FOLDER/textfile.txt" using the TUS protocol on the WebDAV API
     Then as "Alice" file "/FOLDER/textfile.txt" should exist
     And the content of file "/FOLDER/textfile.txt" for user "Alice" should be "uploaded content"
@@ -44,7 +42,6 @@ Feature: upload file to shared folder
     And user "Brian" has been added to group "grp1"
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "FOLDER" with group "grp1" with permissions "change"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file with content "uploaded content" to "/Shares/FOLDER/textfile.txt" using the TUS protocol on the WebDAV API
     Then as "Alice" file "/FOLDER/textfile.txt" should exist
     And the content of file "/FOLDER/textfile.txt" for user "Alice" should be "uploaded content"
@@ -59,7 +56,6 @@ Feature: upload file to shared folder
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has uploaded file with content "original content" to "/FOLDER/textfile.txt"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file with content "overwritten content" to "/Shares/FOLDER/textfile.txt" using the TUS protocol on the WebDAV API
     Then as "Alice" file "/FOLDER/textfile.txt" should exist
     And the content of file "/FOLDER/textfile.txt" for user "Alice" should be "overwritten content"
@@ -73,7 +69,6 @@ Feature: upload file to shared folder
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian" with permissions "read"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" uploads file with content "uploaded content" to "/Shares/FOLDER/textfile.txt" using the TUS protocol on the WebDAV API
     Then as "Brian" file "/Shares/FOLDER/textfile.txt" should not exist
     Examples:
@@ -86,7 +81,6 @@ Feature: upload file to shared folder
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Alice" has created a new TUS resource on the WebDAV API with these headers:
       | Upload-Length   | 5                                     |
       #    L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt
@@ -105,7 +99,6 @@ Feature: upload file to shared folder
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Alice" has created a new TUS resource on the WebDAV API with these headers:
       | Upload-Length   | 5                                     |
       #    L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt
@@ -128,7 +121,6 @@ Feature: upload file to shared folder
       | Upload-Metadata | filename dGV4dEZpbGUudHh0 |
     And user "Alice" has uploaded file with checksum "SHA1 8cb2237d0679ca88db6464eac60da96345513964" to the last created TUS Location with offset "0" and content "12345" using the TUS protocol on the WebDAV API
     And user "Alice" has shared file "/textFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/textFile.txt" offered by user "Alice"
     When user "Brian" requests the checksum of "/Shares/textFile.txt" via propfind
     Then the HTTP status code should be "207"
     And the webdav checksum should match "SHA1:8cb2237d0679ca88db6464eac60da96345513964 MD5:827ccb0eea8a706c4c34a16891f84e7b ADLER32:02f80100"
@@ -146,7 +138,6 @@ Feature: upload file to shared folder
       | Upload-Metadata | filename dGV4dEZpbGUudHh0 |
     And user "Alice" has uploaded file with checksum "SHA1 8cb2237d0679ca88db6464eac60da96345513964" to the last created TUS Location with offset "0" and content "12345" using the TUS protocol on the WebDAV API
     And user "Alice" has shared file "/textFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/textFile.txt" offered by user "Alice"
     When user "Brian" downloads file "/Shares/textFile.txt" using the WebDAV API
     Then the HTTP status code should be "200"
     And the header checksum should match "SHA1:8cb2237d0679ca88db6464eac60da96345513964"
@@ -160,7 +151,6 @@ Feature: upload file to shared folder
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" creates a new TUS resource on the WebDAV API with these headers:
       | Tus-Resumable   | 1.0.0                                         |
       | Upload-Length   | 16                                            |
@@ -180,7 +170,6 @@ Feature: upload file to shared folder
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     When user "Brian" creates a new TUS resource on the WebDAV API with these headers:
       | Tus-Resumable   | 1.0.0                                         |
       | Upload-Length   | 16                                            |
@@ -199,7 +188,6 @@ Feature: upload file to shared folder
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Alice" has created a new TUS resource on the WebDAV API with these headers:
       | Upload-Length   | 5                                     |
       #    L0ZPTERFUi90ZXh0RmlsZS50eHQ= is the base64 encode of /FOLDER/textFile.txt
@@ -223,7 +211,6 @@ Feature: upload file to shared folder
     When user "Alice" sends a chunk to the last created TUS Location with offset "0" and data "01234" with checksum "MD5 4100c4d44da9177247e44a5fc1546778" using the TUS protocol on the WebDAV API
     And user "Alice" sends a chunk to the last created TUS Location with offset "5" and data "56789" with checksum "MD5 099ebea48ea9666a7da2177267983138" using the TUS protocol on the WebDAV API
     And user "Alice" shares file "textFile.txt" with user "Brian" using the sharing API
-    And user "Brian" accepts share "/textFile.txt" offered by user "Alice" using the sharing API
     Then the HTTP status code should be "200"
     And the content of file "/Shares/textFile.txt" for user "Brian" should be "0123456789"
     Examples:
@@ -236,7 +223,6 @@ Feature: upload file to shared folder
     Given using <dav-path-version> DAV path
     And user "Alice" has created folder "/FOLDER"
     And user "Alice" has shared folder "/FOLDER" with user "Brian"
-    And user "Brian" has accepted share "/FOLDER" offered by user "Alice"
     And user "Brian" creates a new TUS resource on the WebDAV API with these headers:
       | Tus-Resumable   | 1.0.0                                         |
       | Upload-Length   | 10                                            |
@@ -261,7 +247,6 @@ Feature: upload file to shared folder
       | Upload-Metadata | filename dGV4dEZpbGUudHh0 |
     And user "Alice" has uploaded file with checksum "SHA1 c1dab0c0864b6ac9bdd3743a1408d679f1acd823" to the last created TUS Location with offset "0" and content "original content" using the TUS protocol on the WebDAV API
     And user "Alice" has shared file "/textFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/textFile.txt" offered by user "Alice"
     When user "Brian" overwrites recently shared file with offset "0" and data "overwritten content" with checksum "SHA1 fe990d2686a0fc86004efc31f5bf2475a45d4905" using the TUS protocol on the WebDAV API with these headers:
       | Upload-Length   | 19                                    |
         #    dGV4dEZpbGUudHh0 is the base64 encode of /Shares/textFile.txt
@@ -282,7 +267,6 @@ Feature: upload file to shared folder
       | Upload-Metadata | filename dGV4dEZpbGUudHh0 |
     And user "Alice" has uploaded file with checksum "SHA1 c1dab0c0864b6ac9bdd3743a1408d679f1acd823" to the last created TUS Location with offset "0" and content "original content" using the TUS protocol on the WebDAV API
     And user "Alice" has shared file "/textFile.txt" with user "Brian"
-    And user "Brian" has accepted share "/textFile.txt" offered by user "Alice"
     When user "Brian" overwrites recently shared file with offset "0" and data "overwritten content" with checksum "SHA1 fe990d2686a0fc86004efc31f5bf2475a45d4906" using the TUS protocol on the WebDAV API with these headers:
       | Upload-Length   | 19                                    |
       #    dGV4dEZpbGUudHh0 is the base64 encode of /Shares/textFile.txt

tests/config/drone/banned-password-list.txt

@@ -1,3 +1,4 @@
 password
+12345678
 123
 ownCloud

tests/parallelDeployAcceptance/features/apiShareManagement/acceptShares.feature

@@ -16,9 +16,6 @@ Feature: sharing files and folders
   Scenario: accept a pending share
     Given user "Alice" has shared folder "/textfile.txt" with user "Brian"
     And using "ocis" as owncloud selector
-    When user "Brian" accepts share "/Shares/textfile.txt" offered by user "Alice" using the sharing API
-    Then the OCS status code should be "100"
-    And the HTTP status code should be "200"
     And the sharing API should report to user "Brian" that these shares are in the accepted state
       | path                 |
       | /Shares/textfile.txt |