🤝 Implement OCM v1.1 + 1.2

[provokateurin]

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
We don't support the latest version of OCM: https://github.com/cs3org/OCM-API/releases/tag/v1.1.0

Describe the solution you'd like
Implement the new v1.1 version

[mickenordin]

I think the only issue that is left for OCM 1.1.0 after #51113 is to fix the apiVersion in the discovery endpoint. This is the code and comment:

'apiVersion' => '1.0-proposal1', // deprecated, but keep it to stay compatible with old version

server/lib/private/OCM/Model/OCMProvider.php

Line 236 in 9dea618

'apiVersion' => '1.0-proposal1', // deprecated, but keep it to stay compatible with old version

I think this is a misstake, the apiVersion is not deprecated (https://cs3org.github.io/OCM-API/docs.html?branch=v1.1.0&repo=OCM-API&user=cs3org#/paths/~1ocm-provider/get), and it should say 1.1.0 now. I cant find any code that relies on it being set specifically to 1.0-proposal1 either.: https://github.com/search?q=org%3Anextcloud+1.0-proposal1&type=code

So I think it should be fine to just change it to the real thing.

Then we might want to be able to accept newer type of share (i.e. webdav part of multi and the newer form of webdav single protocol) but as long as we reply 501 to any share type we don't understand, I think we should be fine to call us 1.1.0 after we have invites and capabilities/provider set in the discovery that we will have after #51113