-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different DAV permissions for space members on the same resource #3373
Comments
The issue is this line here: https://github.com/cs3org/reva/blob/7ea3143d9a2a7b56826465ac2971e279e6f2667c/internal/http/services/owncloud/ocdav/propfind/propfind.go#L711 We assume that not being the owner on a resource means that it was shared with us. Now with the project spaces this is not true and we can't test the share status like that. Actually I think we should generally rethink the "owner" attribute since technically everything in the back-end is contained in different spaces. If we would get rid of the "owner" attribute we could handle all spaces the same, including personal spaces. |
I had the idea that when doing a |
when accessing
we may need to remember the space id and pass it all the way down to |
fixed |
First off, I'm not 100% sure if this is a bug. But what I'm experiencing:
admin
einstein
as manager for this spaceadmin
, create a folderfolderInsideSpace
inside the spaceIMO the DAV permissions in the PROPFIND request for
folderInsideSpace
should look the same for bothadmin
andeinstein
. But I'm seeing differences:For the user
admin
, I get the permissionsRDNVCK
. For the usereinstein
, I getSRDNVCK
. So the latter includesS
, which Web uses as indicator if a resource is shared - which is not the case here.The text was updated successfully, but these errors were encountered: