-
Notifications
You must be signed in to change notification settings - Fork 180
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
Managing Space memberships #2740
Comments
Jörn Friedrich Dreyer commented: In oc10 the storage property of a share is only used for internal joins to check if a path is accessible. The share2.0 api implementation actually has no storage or storageid property. |
David Christofas commented: https://github.com/C0rby/reva/tree/space-membership
|
David Christofas commented: cs3org/reva#2250 |
As a manager of a Space I want to add users to the Space so that they can collaborate.
As a manager of a Space I want to control what Space members are allowed to do.
As a manager of a Space I want to remove users from the Space so that they can not access the Space anymore.
!Spaces.png!
Concept
A space is a share with additional properties, eg. quota.
Graph and OCS API implement the ownCloud business layer:
Questions
The reason is that only managers should be able to manage space properties. We can implement this restriction in the graph api, but editors could just overwrite the file using webdav. This would be solved by the negative permissions CERN is planning.
This loophole is currently accepted. It needs to be resolved before GA. One option would be to move the .spaces folder outside of the space and not expose them via webdav, which has the drawback that managers cannot edit the .spaces folder via webav when syncing it to the local disk.
Related services
/me/drives
endpointAC
The text was updated successfully, but these errors were encountered: