Closed saw-jan closed 1 week ago
I can confirm. cc @rhafer
curl -XPROPFIND 'https://ocis-server:9200/remote.php/dav/files/admin/Shares/remoteFolder' -uadmin:admin -vk
curl -XPROPFIND 'https://ocis-server:9200/remote.php/dav/spaces/{shares-space-id}/remoteFolder' -uadmin:admin -vk
Both of these can only work for "normal" user and group shares. As requests to these paths are handled by the sharestorageprovider. Federated shares are handled by a different storageprovider.
AFAICS there is currently no way to list received ocm shares via webdav (or access them by mount path). You can get the id via sharedWithMe on the graph service (like web does)
curl -k -u moss:vista 'https://ocis-federation.owncloud.test/graph/v1beta1/me/drive/sharedWithMe'
Then take the id
values of the embedded remoteItem
.
yes, remoteItem id from sharedWithMe
and mount-point id from me/drives
both work.
If this is expected and there will be no further improvements/changes, then we can close this one.
Steps to reproduce
remoteFolder
)curl -XPROPFIND 'https://ocis-server:9200/remote.php/dav/spaces/{shares-space-id}/remoteFolder' -uadmin:admin -vk
But the share is accessible using mount-point-id and remote-item-id
Since this is a remote share, maybe the behaviour is expected.
Related: https://github.com/owncloud/web/issues/11753 Web using remote id: https://github.com/owncloud/web/pull/11758