Fix ocm end-point discovery discovery

[schiessle]

fix #14247

[rullzer]

TODO:

• Update nginx docs

[schiessle]

@rullzer updated the documentation as well: nextcloud/documentation#1260

[rullzer]

@MorrisJobke just editing it there is enough to also trigger the recreation of htacceess during update right?

[MorrisJobke]

Please add a setup check to the admin settings to notify users about this.

See for example the well-known check in the browser that does something like this:

server/settings/js/admin.js

Line 251 in 813ff43

OC.SetupChecks.checkWellKnownUrl('/.well-known/webfinger', oc_defaults.docPlaceholderUrl, $('#postsetupchecks').data('check-wellknown') === true && !!oc_appconfig.core.public_webfinger, [200, 501]),

[MorrisJobke]

@MorrisJobke just editing it there is enough to also trigger the recreation of htacceess during update right?

It is written on every update - so yes.

[schiessle]

@MorrisJobke seems like we don't have a similar check for the "ocs-provider" endpoint as well. I'm not sure how to add this quickly. Maybe some of our @nextcloud/javascript experts?

[schiessle]

I added a check for both (while I'm on it), the ocs-provider and the ocm-provider route, see the last two commits

[MorrisJobke]

And let me also rebase to resolve conflicts ...

[schiessle]

@MorrisJobke thanks for taking care of it! 👍

[MorrisJobke]

And let me add some unit tests for it.

[MorrisJobke]

Tested and works 👍

[MorrisJobke]

/backport to stable15

[backportbot-nextcloud]

The backport to stable15 failed. Please do this backport manually.

[MorrisJobke]

Backport in #14312

[MorrisJobke]

@schiessle Is there any reason why this is not put under the /.well-known/ path, because this is the exact purpose of this?