Skip to content

Latest commit

 

History

History
348 lines (298 loc) · 44.6 KB

expected-failures-localAPI-on-OCIS-storage.md

File metadata and controls

348 lines (298 loc) · 44.6 KB

Scenarios from OCIS API tests that are expected to fail with OCIS storage

The expected failures in this file are from features in the owncloud/ocis repo.

Downloading the archive of the resource (files | folder) using resource path is not possible

PATCH request for TUS upload with wrong checksum gives incorrect response

Settings service user can list other peoples assignments

A User can get information of another user with Graph API

Normal user can get expanded members information of a group

Same users can be added in a group multiple time

Users are added in a group with wrong host in host-part of user

Adding the same user as multiple members in a single request results in listing the same user twice in the group

Shared file locking is not possible using different path

Folders can be locked and locking works partially

Anonymous users can unlock a file shared to them through a public link if they get the lock token

Trying to unlock a shared file with sharer's lock token gives 500

Anonymous user trying lock a file shared to them through a public link gives 405

blocksDownload link type is not implemented yet (sharing-ng)

sharee (editor role) MOVE a file by file-id into shared sub-folder returns 502

MOVE a file into same folder with same name returns 404 instead of 403

OCM. admin cannot get federated users if he hasn't connection with them

OCM. federated connection is not dropped when one of the users deletes the connection

OCM. server crash after deleting share for ocm user

same href in REPORT request for all dav-path-version

Shares Jail PROPFIND returns different File IDs for the same item

Readiness check for some services returns 500 status code

[OCM] Users can invite themselves to their own federated connection

[OCM] Hide & Enable Sync fail with received federated shares

[OCM] federated user trying to download file shared with permissions role Secure Viewer returns 500 status code

Delete user containing + in username returns 404 but user gets deleted

creating auth-app token with user-id creates token for the wrong user

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.