Bugfix: Pass remote share id and shared secret in OCM call

[michielbdejong]

In internal/grpc/services/ocmshareprovider/ocmshareprovider.go, pass share.Token as SharedSecret inside the WebDAV protocol details, and use the remote id as the resource id.

This PR also adds some debug messages.

[update-docs]

Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes.

[michielbdejong]

Let's call it ProviderID and then add it here as well:

reva/internal/http/services/ocmd/shares.go

Line 67 in d1eacc5

ResourceID string `json:"resourceId" validate:"required"` // unique identifier of the resource at provider side

[michielbdejong]

In

reva/internal/http/services/ocmd/shares.go

Line 155 in d1eacc5

ResourceId: req.ResourceID,

it passes into CS3APIs

[michielbdejong]

Let's add back provider_id in https://github.com/cs3org/cs3apis/blame/441d6c62a5b8cf8e3f3f3d1ae8a38cc1057d6850/cs3/ocm/core/v1beta1/ocm_core_api.proto#L63

[michielbdejong]

And also in ocm.ReceivedShare

reva/internal/grpc/services/ocmcore/ocmcore.go

Line 119 in d1eacc5

share, err := s.repo.StoreReceivedShare(ctx, &ocm.ReceivedShare{

[michielbdejong]

As discussed in the Zoom call now, @gmgigi96 will update this PR so that is uses provider_id instead of resource_id at all levels and layers it passes through.

[gmgigi96]

@michielbdejong @glpatcern I have pushed my changes, can you review?
In particular, Michiel, can you fix the tests for the nextcloud driver?

[gmgigi96]

I have opened cs3org/cs3apis#209 for the needed changes in the CS3APIs

[michielbdejong]

@gmgigi96 cs3org/cs3apis#209 is merged so you can revert 7e55510 right?