implement OCM wellknown for discovery

[butonic]

The wellknown service now implements the /.well-known/ocm endpoint for OCM discovery. The unused endpoints for openid connect and webfinger have been removed. This aligns the wellknown implementation with the master branch.

Categorizing as 'Enhancement' because the existing service was unused in ocis.

[glpatcern]

Good you're looking after this @butonic ! but don't forget the legacy endpoint must remain.

And more in general: what about having a checkpoint meeting on what is pure OCM vs what is ScienceMesh etc.? I didn't receive any reply to my email in July but people should be back in the coming days. Let's sort out the details by email?

[butonic]

so ... discovery is only part of sciencemesh?

[glpatcern]

so ... discovery is only part of sciencemesh?

how is that related to the wellknown endpoint? Anyway, discovery is part of OCM.

[butonic]

@glpatcern which legacy endpoints exactly? the old oidc and webfinger stups I removed?

👀

When a sending server allows sharing to any internet-hosted receiving server, then discovery can happen from the sharee address, using the /.well-known/ocm (or /ocm-provider, for backwards compatibility) URL that receiving servers SHOULD provide according to this specification.

Ah so you mean /ocm-provider? it should render the exact same content, right?

regarding a checkpoint meeting: that would be welcome ... need to find a timeslot ...

[glpatcern]

Ah so you mean /ocm-provider? it should render the exact same content, right?

Yes that's it.

regarding a checkpoint meeting: that would be welcome ... need to find a timeslot ...

I can revive the mail thread and propose some slots, we should all be back and it's hopefully easy to find one.