You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 18, 2021. It is now read-only.
Just some notes from my debugging sessions:
In internal/http/services/owncloud/ocs/shares.go#createShare the following things happen.
The persmissions 0 and 32 are mapped to the role legacy. Further down in role2CS3Permissions the role legacy is unknown so an error is returned.
Now with asCS3Permissions we check if the permission is a CS3 permission.
We create a new ResourcePermission instance and check if any of the CS3 permissions match, they don't but we already created a new permission instance (with default values) and return it.
Now the method continues as ususal and calls CreateShare on the gateway which routes the request to the handler and from now on the permissions are never checked but the share will be created.
My guess is that the support for legacy roles is missing.
sharing a resource with permission
0
or32
should fail with HTTP 400The text was updated successfully, but these errors were encountered: