oCIS share jail

[kulmann]

With owncloud/web#6593 being merged ownCloud Web will use new webdav endpoints for accessing the content of shares. This relies on the capability spaces.share_jail being true (which is the default in oCIS and does not and never will exist in oc10). Most importantly the new webdav endpoint for the personal space of a user does not list shares anymore. It's a conscious product decision to have a clear separation of personal files and shares.

I guess (@micbar please confirm) the old webdav endpoint for the user home (remote.php/dav/files/<username>) will continue to exist for quite some time to give all clients a chance to adapt. So there is probably no immediate action needed. But at some point it will make sense to teach the middleware how to access personal files and shares with the new spaces webdav endpoints.

Some technical details:

• personal space of a user is dav/spaces/<uuid of the user>/relative/path/to/a/file
• accepted shares are accessed via the so called share jail, which at the moment has a hardcoded storage id, resulting in endpoints per share like this: dav/spaces/<hardcoded share jail id>!<share id>/relative/path/to/a/file
• project spaces are the same as user spaces: dav/spaces/<uuid of the space>/relative/path/to/a/file

Gherkin like the following will have to change for this: And user "Alice" has accepted the share "Shares/simple-folder" offered by user "Brian" in the server. Does it make sense that you invest some time into a concept for this? We won't teach the nightwatch acceptance tests in web about project spaces, it doesn't make sense to switch them over to the share jail if they are the only consumer of these test steps, and the playwright e2e tests in web don't use the test middleware. Still wanted you to be aware of the change. Please reach out with any question.