sharing-v1.feature 36.8 KB
Newer Older
Sergio Bertolin's avatar
Sergio Bertolin committed
1
2
3
Feature: sharing
  Background:
    Given using api version "1"
4
    Given using old dav path
Sergio Bertolin's avatar
Sergio Bertolin committed
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

  Scenario: Creating a new share with user
    Given user "user0" exists
    And user "user1" exists
    And As an "user0"
    When sending "POST" to "/apps/files_sharing/api/v1/shares" with
      | path | welcome.txt |
      | shareWith | user1 |
      | shareType | 0 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"

  Scenario: Creating a share with a group
    Given user "user0" exists
    And user "user1" exists
    And group "sharing-group" exists
    And As an "user0"
    When sending "POST" to "/apps/files_sharing/api/v1/shares" with
      | path | welcome.txt |
      | shareWith | sharing-group |
      | shareType | 1 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"

29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
  Scenario: Creating a new share with user who already received a share through their group
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "sharing-group" exists
    And user "user1" belongs to group "sharing-group"
    And file "welcome.txt" of user "user0" is shared with group "sharing-group"
    And As an "user0"
    Then sending "POST" to "/apps/files_sharing/api/v1/shares" with
      | path | welcome.txt |
      | shareWith | user1 |
      | shareType | 0 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"

Sergio Bertolin's avatar
Sergio Bertolin committed
44
45
46
  Scenario: Creating a new public share
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
47
    When creating a share with
Sergio Bertolin's avatar
Sergio Bertolin committed
48
49
50
51
52
53
54
55
56
      | path | welcome.txt |
      | shareType | 3 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Public shared file "welcome.txt" can be downloaded

  Scenario: Creating a new public share with password
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
57
    When creating a share with
Sergio Bertolin's avatar
Sergio Bertolin committed
58
59
60
61
62
63
64
      | path | welcome.txt |
      | shareType | 3 |
      | password | publicpw |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Public shared file "welcome.txt" with password "publicpw" can be downloaded

65
66
67
  Scenario: Creating a new public share of a folder
   Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
68
    When creating a share with
69
70
71
72
73
74
75
76
77
78
      | path | FOLDER |
      | shareType | 3 |
      | password | publicpw |
      | expireDate | +3 days |
      | publicUpload | true |
      | permissions | 7 |
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
79
      | permissions | 15 |
80
81
82
      | expiration | +3 days |
      | url | AN_URL |
      | token | A_TOKEN |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
83
      | mimetype | httpd/unix-directory |
84

Sergio Bertolin's avatar
Sergio Bertolin committed
85
86
87
  Scenario: Creating a new public share with password and adding an expiration date
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
88
    When creating a share with
Sergio Bertolin's avatar
Sergio Bertolin committed
89
90
91
      | path | welcome.txt |
      | shareType | 3 |
      | password | publicpw |
92
93
    And Updating last share with
      | expireDate | +3 days |
Sergio Bertolin's avatar
Sergio Bertolin committed
94
95
96
97
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Public shared file "welcome.txt" with password "publicpw" can be downloaded

98
  Scenario: Creating a new public share, updating its expiration date and getting its info
99
100
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
101
    When creating a share with
102
103
104
105
      | path | FOLDER |
      | shareType | 3 |
    And Updating last share with
      | expireDate | +3 days |
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
    And Getting info of last share 
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | folder |
      | item_source | A_NUMBER |
      | share_type | 3 |
      | file_source | A_NUMBER |
      | file_target | /FOLDER |
      | permissions | 1 |
      | stime | A_NUMBER |
      | expiration | +3 days |
      | token | A_TOKEN |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | displayname_owner | user0 |
      | url | AN_URL |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
127
      | mimetype | httpd/unix-directory |
128
129
130
131

  Scenario: Creating a new public share, updating its password and getting its info
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
132
    When creating a share with
133
134
135
      | path | FOLDER |
      | shareType | 3 |
    And Updating last share with 
136
      | password | publicpw |
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
    And Getting info of last share 
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | folder |
      | item_source | A_NUMBER |
      | share_type | 3 |
      | file_source | A_NUMBER |
      | file_target | /FOLDER |
      | permissions | 1 |
      | stime | A_NUMBER |
      | token | A_TOKEN |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | displayname_owner | user0 |
      | url | AN_URL |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
157
      | mimetype | httpd/unix-directory |
158
159
160
161

  Scenario: Creating a new public share, updating its permissions and getting its info
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
162
    When creating a share with
163
164
165
      | path | FOLDER |
      | shareType | 3 |
    And Updating last share with
166
167
168
169
170
171
172
173
174
175
176
      | permissions | 7 |
    And Getting info of last share 
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | folder |
      | item_source | A_NUMBER |
      | share_type | 3 |
      | file_source | A_NUMBER |
      | file_target | /FOLDER |
177
      | permissions | 15 |
178
179
180
181
182
183
184
185
186
      | stime | A_NUMBER |
      | token | A_TOKEN |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | displayname_owner | user0 |
      | url | AN_URL |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
187
      | mimetype | httpd/unix-directory |
188

189
190
191
  Scenario: Creating a new public share, updating publicUpload option and getting its info
    Given user "user0" exists
    And As an "user0"
Sergio Bertolin's avatar
Sergio Bertolin committed
192
    When creating a share with
193
194
195
196
197
198
199
200
201
202
203
204
205
206
      | path | FOLDER |
      | shareType | 3 |
    And Updating last share with
      | publicUpload | true |
    And Getting info of last share 
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | folder |
      | item_source | A_NUMBER |
      | share_type | 3 |
      | file_source | A_NUMBER |
      | file_target | /FOLDER |
207
      | permissions | 15 |
208
209
210
211
212
213
214
215
216
      | stime | A_NUMBER |
      | token | A_TOKEN |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | displayname_owner | user0 |
      | url | AN_URL |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
217
      | mimetype | httpd/unix-directory |
218

219
220
221
  Scenario: getting all shares of a user using that user
    Given user "user0" exists
    And user "user1" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
222
    And file "textfile0.txt" of user "user0" is shared with user "user1"
223
224
225
226
    And As an "user0"
    When sending "GET" to "/apps/files_sharing/api/v1/shares"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
227
    And File "textfile0.txt" should be included in the response
228
229

  Scenario: getting all shares of a user using another user
230
231
    Given user "user0" exists
    And user "user1" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
232
    And file "textfile0.txt" of user "user0" is shared with user "user1"
233
234
235
236
    And As an "admin"
    When sending "GET" to "/apps/files_sharing/api/v1/shares"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
237
    And File "textfile0.txt" should not be included in the response
238

239
240
241
242
243
  Scenario: getting all shares of a file
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
244
245
    And file "textfile0.txt" of user "user0" is shared with user "user1"
    And file "textfile0.txt" of user "user0" is shared with user "user2"
246
247
248
249
250
251
252
253
    And As an "user0"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?path=textfile0.txt"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And User "user1" should be included in the response
    And User "user2" should be included in the response
    And User "user3" should not be included in the response

Roeland Jago Douma's avatar
Roeland Jago Douma committed
254
255
256
257
258
259
260
261
262
263
264
265
266
267
  Scenario: getting all shares of a file with reshares
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And file "textfile0.txt" of user "user0" is shared with user "user1"
    And file "textfile0 (2).txt" of user "user1" is shared with user "user2"
    And As an "user0"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?reshares=true&path=textfile0.txt"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And User "user1" should be included in the response
    And User "user2" should be included in the response
    And User "user3" should not be included in the response
268

Sergio Bertolin's avatar
Sergio Bertolin committed
269
270
271
272
273
274
275
276
277
278
279
280
281
282
  Scenario: Reshared files can be still accessed if a user in the middle removes it.
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user3" exists
    And file "textfile0.txt" of user "user0" is shared with user "user1"
    And file "textfile0 (2).txt" of user "user1" is shared with user "user2"
    And file "textfile0 (2).txt" of user "user2" is shared with user "user3"
    And As an "user1"
    When User "user1" deletes file "/textfile0 (2).txt"
    And As an "user3"
    And Downloading file "/textfile0 (2).txt" with range "bytes=1-7"
    Then Downloaded content should be "wnCloud"

283
284
285
  Scenario: getting share info of a share
    Given user "user0" exists
    And user "user1" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
286
    And file "textfile0.txt" of user "user0" is shared with user "user1"
287
288
289
290
291
292
293
294
295
296
297
    And As an "user0"
    When Getting info of last share
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | file |
      | item_source | A_NUMBER |
      | share_type | 0 |
      | share_with | user1 |
      | file_source | A_NUMBER |
298
      | file_target | /textfile0.txt |
299
      | path | /textfile0.txt |
300
      | permissions | 19 |
301
302
303
304
305
306
307
308
      | stime | A_NUMBER |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | share_with_displayname | user1 |
      | displayname_owner | user0 |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
309
      | mimetype          | text/plain |
310

311
312
313
314
315
316
  Scenario: keep group permissions in sync
    Given As an "admin"
    Given user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And user "user1" belongs to group "group1"
Sergio Bertolin's avatar
Sergio Bertolin committed
317
    And file "textfile0.txt" of user "user0" is shared with group "group1"
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
    And User "user1" moved file "/textfile0.txt" to "/FOLDER/textfile0.txt"
    And As an "user0"
    When Updating last share with
      | permissions | 1 |
    And Getting info of last share
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And Share fields of last share match with
      | id | A_NUMBER |
      | item_type | file |
      | item_source | A_NUMBER |
      | share_type | 1 |
      | file_source | A_NUMBER |
      | file_target | /textfile0.txt |
      | permissions | 1 |
      | stime | A_NUMBER |
      | storage | A_NUMBER |
      | mail_send | 0 |
      | uid_owner | user0 |
      | storage_id | home::user0 |
      | file_parent | A_NUMBER |
      | displayname_owner | user0 |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
340
      | mimetype          | text/plain |
341

342
343
344
  Scenario: Sharee can see the share
    Given user "user0" exists
    And user "user1" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
345
    And file "textfile0.txt" of user "user0" is shared with user "user1"
346
347
348
    And As an "user1"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
    Then the OCS status code should be "100"
349
350
351
    And the HTTP status code should be "200"
    And last share_id is included in the answer

Roeland Jago Douma's avatar
Roeland Jago Douma committed
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
  Scenario: Sharee can see the filtered share
    Given user "user0" exists
    And user "user1" exists
    And file "textfile0.txt" of user "user0" is shared with user "user1"
    And file "textfile1.txt" of user "user0" is shared with user "user1"
    And As an "user1"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true&path=textfile1 (2).txt"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And last share_id is included in the answer

  Scenario: Sharee can't see the share that is filtered out
    Given user "user0" exists
    And user "user1" exists
    And file "textfile0.txt" of user "user0" is shared with user "user1"
    And file "textfile1.txt" of user "user0" is shared with user "user1"
    And As an "user1"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true&path=textfile0 (2).txt"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And last share_id is not included in the answer

374
375
376
377
378
379
380
381
382
383
  Scenario: Sharee can see the group share
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group0" exists
    And user "user1" belongs to group "group0"
    And file "textfile0.txt" of user "user0" is shared with group "group0"
    And As an "user1"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
    Then the OCS status code should be "100"
384
385
386
    And the HTTP status code should be "200"
    And last share_id is included in the answer

Sergio Bertolin's avatar
Sergio Bertolin committed
387
388
389
390
391
392
393
394
395
396
397
398
399
  Scenario: User is not allowed to reshare file
    As an "admin"
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And As an "user0"
    And creating a share with
      | path | /textfile0.txt |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 8 |
    And As an "user1"
    When creating a share with
400
      | path | /textfile0 (2).txt |
Sergio Bertolin's avatar
Sergio Bertolin committed
401
402
403
404
405
406
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 31 |
    Then the OCS status code should be "404"
    And the HTTP status code should be "200"

407
408
409
410
411
412
413
414
415
416
417
418
419
  Scenario: User is not allowed to reshare file with more permissions
    As an "admin"
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And As an "user0"
    And creating a share with
      | path | /textfile0.txt |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 16 |
    And As an "user1"
    When creating a share with
420
      | path | /textfile0 (2).txt |
421
422
423
424
425
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 31 |
    Then the OCS status code should be "404"
    And the HTTP status code should be "200"
Sergio Bertolin's avatar
Sergio Bertolin committed
426

427
428
429
430
  Scenario: Get a share with a user which didn't received the share 
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
431
    And file "textfile0.txt" of user "user0" is shared with user "user1"
432
433
434
435
436
    And As an "user2"
    When Getting info of last share 
    Then the OCS status code should be "404" 
    And the HTTP status code should be "200"

437
438
439
440
441
442
  Scenario: Share of folder and sub-folder to same user - core#20645
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group0" exists
    And user "user1" belongs to group "group0"
Sergio Bertolin's avatar
Sergio Bertolin committed
443
444
    And file "/PARENT" of user "user0" is shared with user "user1"
    When file "/PARENT/CHILD" of user "user0" is shared with group "group0"
445
446
447
448
449
450
    Then user "user1" should see following elements
      | /FOLDER/ |
      | /PARENT/ |
      | /CHILD/ |
      | /PARENT/parent.txt |
      | /CHILD/child.txt |
451
452
    And the HTTP status code should be "200"

453
  Scenario: Share a file by multiple channels 
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And group "group0" exists
    And user "user1" belongs to group "group0"
    And user "user2" belongs to group "group0"
    And user "user0" created a folder "/common"
    And user "user0" created a folder "/common/sub"
    And file "common" of user "user0" is shared with group "group0"
    And file "textfile0.txt" of user "user1" is shared with user "user2"
    And User "user1" moved file "/textfile0.txt" to "/common/textfile0.txt"
    And User "user1" moved file "/common/textfile0.txt" to "/common/sub/textfile0.txt"
    And As an "user2"
    When Downloading file "/common/sub/textfile0.txt" with range "bytes=9-17"
    Then Downloaded content should be "test text"
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
    And Downloaded content when downloading file "/textfile0.txt" with range "bytes=9-17" should be "test text"
    And user "user2" should see following elements
      | /common/sub/textfile0.txt |

  Scenario: Share a file by multiple channels
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And group "group0" exists
    And user "user1" belongs to group "group0"
    And user "user2" belongs to group "group0"
    And user "user0" created a folder "/common"
    And user "user0" created a folder "/common/sub"
    And file "common" of user "user0" is shared with group "group0"
    And file "textfile0.txt" of user "user1" is shared with user "user2"
    And User "user1" moved file "/textfile0.txt" to "/common/textfile0.txt"
    And User "user1" moved file "/common/textfile0.txt" to "/common/sub/textfile0.txt"
    And As an "user2"
    When Downloading file "/textfile0.txt" with range "bytes=9-17"
    Then Downloaded content should be "test text"
491
492
493
    And user "user2" should see following elements
      | /common/sub/textfile0.txt |

494
495
496
497
498
499
  Scenario: Delete all group shares
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And user "user1" belongs to group "group1"
Sergio Bertolin's avatar
Sergio Bertolin committed
500
    And file "textfile0.txt" of user "user0" is shared with group "group1"
501
502
503
504
505
506
507
508
509
    And User "user1" moved file "/textfile0.txt" to "/FOLDER/textfile0.txt"
    And As an "user0"
    And Deleting last share
    And As an "user1"
    When sending "GET" to "/apps/files_sharing/api/v1/shares?shared_with_me=true"
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"
    And last share_id is not included in the answer

510
511
512
  Scenario: delete a share
    Given user "user0" exists
    And user "user1" exists
Sergio Bertolin's avatar
Sergio Bertolin committed
513
    And file "textfile0.txt" of user "user0" is shared with user "user1"
514
515
516
517
518
    And As an "user0"
    When Deleting last share
    Then the OCS status code should be "100"
    And the HTTP status code should be "200"

Roeland Jago Douma's avatar
Roeland Jago Douma committed
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
  Scenario: Keep usergroup shares (#22143)
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And group "group" exists
    And user "user1" belongs to group "group"
    And user "user2" belongs to group "group"
    And user "user0" created a folder "/TMP"
    And file "TMP" of user "user0" is shared with group "group"
    And user "user1" created a folder "/myFOLDER"
    And User "user1" moves file "/TMP" to "/myFOLDER/myTMP"
    And user "user2" does not exist
    And user "user1" should see following elements
      | /myFOLDER/myTMP/ |
534
535

  Scenario: Check quota of owners parent directory of a shared file
536
    Given using old dav path
537
538
539
540
541
542
543
544
    And As an "admin"
    And user "user0" exists
    And user "user1" exists
    And user "user1" has a quota of "0"
    And User "user0" moved file "/welcome.txt" to "/myfile.txt"
    And file "myfile.txt" of user "user0" is shared with user "user1"
    When User "user1" uploads file "data/textfile.txt" to "/myfile.txt"
    Then the HTTP status code should be "204"
545
546
547
548
549
550
551

  Scenario: Don't allow sharing of the root
    Given user "user0" exists
    And As an "user0"
    When creating a share with
      | path | / |
      | shareType | 3 |
Roeland Jago Douma's avatar
Roeland Jago Douma committed
552
553
554
555
556
557
558
559
560
561
562
563
564
    Then the OCS status code should be "403"

  Scenario: Allow modification of reshare
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user0" created a folder "/TMP"
    And file "TMP" of user "user0" is shared with user "user1"
    And file "TMP" of user "user1" is shared with user "user2"
    And As an "user1"
    When Updating last share with
      | permissions | 1 |
    Then the OCS status code should be "100"
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585

  Scenario: Do not allow reshare to exceed permissions
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user0" created a folder "/TMP"
    And As an "user0"
    And creating a share with
      | path | /TMP |
      | shareType | 0 |
      | shareWith | user1 |
      | permissions | 21 |
    And As an "user1"
    And creating a share with
      | path | /TMP |
      | shareType | 0 |
      | shareWith | user2 |
      | permissions | 21 |
    When Updating last share with
      | permissions | 31 |
    Then the OCS status code should be "404"
Roeland Jago Douma's avatar
Roeland Jago Douma committed
586
587
588
589
590
591
592
593
594
595
596
597

  Scenario: Only allow 1 link share per file/folder
    Given user "user0" exists
    And As an "user0"
    And creating a share with
      | path | welcome.txt |
      | shareType | 3 |
    When save last share id
    And creating a share with
      | path | welcome.txt |
      | shareType | 3      |
    Then share ids should match
598
599
600
601
602

  Scenario: Correct webdav share-permissions for owned file
    Given user "user0" exists
    And User "user0" uploads file with content "foo" to "/tmp.txt"
    When as "user0" gets properties of folder "/tmp.txt" with
603
604
      |{http://open-collaboration-services.org/ns}share-permissions |
    Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "19"
605
606
607
608
609

  Scenario: Correct webdav share-permissions for received file with edit and reshare permissions
    Given user "user0" exists
    And user "user1" exists
    And User "user0" uploads file with content "foo" to "/tmp.txt"
610
    And file "/tmp.txt" of user "user0" is shared with user "user1"
611
    When as "user1" gets properties of folder "/tmp.txt" with
612
613
      |{http://open-collaboration-services.org/ns}share-permissions |
    Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "19"
614
615
616
617
618
619
620
621
622
623

  Scenario: Correct webdav share-permissions for received file with edit permissions but no reshare permissions
    Given user "user0" exists
    And user "user1" exists
    And User "user0" uploads file with content "foo" to "/tmp.txt"
    And file "tmp.txt" of user "user0" is shared with user "user1"
    And As an "user0"
    And Updating last share with
      | permissions | 3 |
    When as "user1" gets properties of folder "/tmp.txt" with
624
625
      |{http://open-collaboration-services.org/ns}share-permissions |
    Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "3"
626
627
628
629
630
631
632
633
634
635

  Scenario: Correct webdav share-permissions for received file with reshare permissions but no edit permissions
    Given user "user0" exists
    And user "user1" exists
    And User "user0" uploads file with content "foo" to "/tmp.txt"
    And file "tmp.txt" of user "user0" is shared with user "user1"
    And As an "user0"
    And Updating last share with
      | permissions | 17 |
    When as "user1" gets properties of folder "/tmp.txt" with
636
637
      |{http://open-collaboration-services.org/ns}share-permissions |
    Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "17"
638
639
640
641
642

  Scenario: Correct webdav share-permissions for owned folder
    Given user "user0" exists
    And user "user0" created a folder "/tmp"
    When as "user0" gets properties of folder "/" with
643
644
      |{http://open-collaboration-services.org/ns}share-permissions |
    Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "31"
645
646
647
648
649
650
651

  Scenario: Correct webdav share-permissions for received folder with all permissions
    Given user "user0" exists
    And user "user1" exists
    And user "user0" created a folder "/tmp"
    And file "/tmp" of user "user0" is shared with user "user1"
    When as "user1" gets properties of folder "/tmp" with
652
653
      |{http://open-collaboration-services.org/ns}share-permissions |
    Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "31"
654
655
656
657
658
659
660
661
662
663

  Scenario: Correct webdav share-permissions for received folder with all permissions but edit
    Given user "user0" exists
    And user "user1" exists
    And user "user0" created a folder "/tmp"
    And file "/tmp" of user "user0" is shared with user "user1"
    And As an "user0"
    And Updating last share with
      | permissions | 29 |
    When as "user1" gets properties of folder "/tmp" with
664
665
      |{http://open-collaboration-services.org/ns}share-permissions |
    Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "29"
666
667
668
669
670
671
672
673
674
675

  Scenario: Correct webdav share-permissions for received folder with all permissions but create
    Given user "user0" exists
    And user "user1" exists
    And user "user0" created a folder "/tmp"
    And file "/tmp" of user "user0" is shared with user "user1"
    And As an "user0"
    And Updating last share with
      | permissions | 27 |
    When as "user1" gets properties of folder "/tmp" with
676
677
      |{http://open-collaboration-services.org/ns}share-permissions |
    Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "27"
678
679
680
681
682
683
684
685
686
687

  Scenario: Correct webdav share-permissions for received folder with all permissions but delete
    Given user "user0" exists
    And user "user1" exists
    And user "user0" created a folder "/tmp"
    And file "/tmp" of user "user0" is shared with user "user1"
    And As an "user0"
    And Updating last share with
      | permissions | 23 |
    When as "user1" gets properties of folder "/tmp" with
688
689
      |{http://open-collaboration-services.org/ns}share-permissions |
    Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "23"
690
691
692
693
694
695
696
697
698
699

  Scenario: Correct webdav share-permissions for received folder with all permissions but share
    Given user "user0" exists
    And user "user1" exists
    And user "user0" created a folder "/tmp"
    And file "/tmp" of user "user0" is shared with user "user1"
    And As an "user0"
    And Updating last share with
      | permissions | 15 |
    When as "user1" gets properties of folder "/tmp" with
700
701
      |{http://open-collaboration-services.org/ns}share-permissions |
    Then the single response should contain a property "{http://open-collaboration-services.org/ns}share-permissions" with value "15"
702

703
  Scenario: unique target names for incoming shares
704
705
706
707
708
709
710
711
712
713
    Given user "user0" exists
    And user "user1" exists
    And user "user2" exists
    And user "user0" created a folder "/foo"
    And user "user1" created a folder "/foo"
    When file "/foo" of user "user0" is shared with user "user2"
    And file "/foo" of user "user1" is shared with user "user2"
    Then user "user2" should see following elements
      | /foo/       |
      | /foo%20(2)/ |
714
715
716
717
718
719
720
721
722
723
724

  Scenario: Creating a new share with a disabled user
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And assure user "user0" is disabled
    And As an "user0"
    When sending "POST" to "/apps/files_sharing/api/v1/shares" with
      | path | welcome.txt |
      | shareWith | user1 |
      | shareType | 0 |
725
726
    Then the OCS status code should be "997"
    And the HTTP status code should be "401"
727
728

  Scenario: Merging shares for recipient when shared from outside with group and member
729
730
    Given using old dav path
    And As an "admin"
731
732
733
734
    And user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And user "user1" belongs to group "group1"
735
736
737
738
739
    And user "user0" created a folder "/merge-test-outside"
    When folder "/merge-test-outside" of user "user0" is shared with group "group1"
    And folder "/merge-test-outside" of user "user0" is shared with user "user1"
    Then as "user1" the folder "/merge-test-outside" exists
    And as "user1" the folder "/merge-test-outside (2)" does not exist
740
741
742
743
744
745
746

  Scenario: Merging shares for recipient when shared from outside with group and member with different permissions
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And user "user1" belongs to group "group1"
747
748
749
750
    And user "user0" created a folder "/merge-test-outside-perms"
    When folder "/merge-test-outside-perms" of user "user0" is shared with group "group1" with permissions 1
    And folder "/merge-test-outside-perms" of user "user0" is shared with user "user1" with permissions 31
    Then as "user1" gets properties of folder "/merge-test-outside-perms" with
751
752
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
753
    And as "user1" the folder "/merge-test-outside-perms (2)" does not exist
754
755
756
757
758
759
760
761
762

  Scenario: Merging shares for recipient when shared from outside with two groups
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And group "group2" exists
    And user "user1" belongs to group "group1"
    And user "user1" belongs to group "group2"
763
764
765
766
767
    And user "user0" created a folder "/merge-test-outside-twogroups"
    When folder "/merge-test-outside-twogroups" of user "user0" is shared with group "group1"
    And folder "/merge-test-outside-twogroups" of user "user0" is shared with group "group2"
    Then as "user1" the folder "/merge-test-outside-twogroups" exists
    And as "user1" the folder "/merge-test-outside-twogroups (2)" does not exist
768
769
770
771
772
773
774
775
776

  Scenario: Merging shares for recipient when shared from outside with two groups with different permissions
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And group "group2" exists
    And user "user1" belongs to group "group1"
    And user "user1" belongs to group "group2"
777
778
779
780
    And user "user0" created a folder "/merge-test-outside-twogroups-perms"
    When folder "/merge-test-outside-twogroups-perms" of user "user0" is shared with group "group1" with permissions 1
    And folder "/merge-test-outside-twogroups-perms" of user "user0" is shared with group "group2" with permissions 31
    Then as "user1" gets properties of folder "/merge-test-outside-twogroups-perms" with
781
782
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
783
    And as "user1" the folder "/merge-test-outside-twogroups-perms (2)" does not exist
784
785
786
787
788
789
790
791
792

  Scenario: Merging shares for recipient when shared from outside with two groups and member
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And group "group2" exists
    And user "user1" belongs to group "group1"
    And user "user1" belongs to group "group2"
793
794
795
796
797
    And user "user0" created a folder "/merge-test-outside-twogroups-member-perms"
    When folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with group "group1" with permissions 1
    And folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with group "group2" with permissions 31
    And folder "/merge-test-outside-twogroups-member-perms" of user "user0" is shared with user "user1" with permissions 1
    Then as "user1" gets properties of folder "/merge-test-outside-twogroups-member-perms" with
798
799
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
800
    And as "user1" the folder "/merge-test-outside-twogroups-member-perms (2)" does not exist
801
802
803
804
805
806

  Scenario: Merging shares for recipient when shared from inside with group
    Given As an "admin"
    And user "user0" exists
    And group "group1" exists
    And user "user0" belongs to group "group1"
807
    And user "user0" created a folder "/merge-test-inside-group"
808
    When folder "/merge-test-inside-group" of user "user0" is shared with group "group1"
809
810
    Then as "user0" the folder "/merge-test-inside-group" exists
    And as "user0" the folder "/merge-test-inside-group (2)" does not exist
811
812
813
814
815
816
817
818

  Scenario: Merging shares for recipient when shared from inside with two groups
    Given As an "admin"
    And user "user0" exists
    And group "group1" exists
    And group "group2" exists
    And user "user0" belongs to group "group1"
    And user "user0" belongs to group "group2"
819
820
821
822
823
824
    And user "user0" created a folder "/merge-test-inside-twogroups"
    When folder "/merge-test-inside-twogroups" of user "user0" is shared with group "group1"
    And folder "/merge-test-inside-twogroups" of user "user0" is shared with group "group2"
    Then as "user0" the folder "/merge-test-inside-twogroups" exists
    And as "user0" the folder "/merge-test-inside-twogroups (2)" does not exist
    And as "user0" the folder "/merge-test-inside-twogroups (3)" does not exist
825
826
827
828
829
830
831
832

  Scenario: Merging shares for recipient when shared from inside with group with less permissions
    Given As an "admin"
    And user "user0" exists
    And group "group1" exists
    And group "group2" exists
    And user "user0" belongs to group "group1"
    And user "user0" belongs to group "group2"
833
834
835
836
    And user "user0" created a folder "/merge-test-inside-twogroups-perms"
    When folder "/merge-test-inside-twogroups-perms" of user "user0" is shared with group "group1"
    And folder "/merge-test-inside-twogroups-perms" of user "user0" is shared with group "group2"
    Then as "user0" gets properties of folder "/merge-test-inside-twogroups-perms" with
837
838
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "RDNVCK"
839
840
    And as "user0" the folder "/merge-test-inside-twogroups-perms (2)" does not exist
    And as "user0" the folder "/merge-test-inside-twogroups-perms (3)" does not exist
841

842
843
844
845
846
847
  Scenario: Merging shares for recipient when shared from outside with group then user and recipient renames in between
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And user "user1" belongs to group "group1"
848
849
    And user "user0" created a folder "/merge-test-outside-groups-renamebeforesecondshare"
    When folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with group "group1"
850
    And User "user1" moved folder "/merge-test-outside-groups-renamebeforesecondshare" to "/merge-test-outside-groups-renamebeforesecondshare-renamed"
851
852
    And folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with user "user1"
    Then as "user1" gets properties of folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" with
853
854
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
855
    And as "user1" the folder "/merge-test-outside-groups-renamebeforesecondshare" does not exist
856
857
858
859
860
861
862

  Scenario: Merging shares for recipient when shared from outside with user then group and recipient renames in between
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And group "group1" exists
    And user "user1" belongs to group "group1"
863
864
    And user "user0" created a folder "/merge-test-outside-groups-renamebeforesecondshare"
    When folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with user "user1"
865
    And User "user1" moved folder "/merge-test-outside-groups-renamebeforesecondshare" to "/merge-test-outside-groups-renamebeforesecondshare-renamed"
866
867
    And folder "/merge-test-outside-groups-renamebeforesecondshare" of user "user0" is shared with group "group1"
    Then as "user1" gets properties of folder "/merge-test-outside-groups-renamebeforesecondshare-renamed" with
868
869
        |{http://owncloud.org/ns}permissions|
    And the single response should contain a property "{http://owncloud.org/ns}permissions" with value "SRDNVCK"
870
    And as "user1" the folder "/merge-test-outside-groups-renamebeforesecondshare" does not exist
871

872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
  Scenario: Empting trashbin
    Given As an "admin"
    And user "user0" exists
    And User "user0" deletes file "/textfile0.txt"
    When User "user0" empties trashbin
    Then the HTTP status code should be "200"

  Scenario: orphaned shares
    Given As an "admin"
    And user "user0" exists
    And user "user1" exists
    And user "user0" created a folder "/common"
    And user "user0" created a folder "/common/sub"
    And file "/common/sub" of user "user0" is shared with user "user1"
    And User "user0" deletes folder "/common"
    When User "user0" empties trashbin
888
    Then as "user1" the folder "/sub" does not exist
889