-
Notifications
You must be signed in to change notification settings - Fork 189
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
Any role can be set during share invite request #8131
Comments
The expected behavior is not correct. We cannot use all roles on all resource types. The roles have conditions. Some can only be applied to space roots some only to shares. but the clients do not need any Knowledge about that. Before creating or updating a permission, they should check what is possible on that specific resource. This is the needed api call https://owncloud.dev/libre-graph-api/#/drives.permissions/ListPermissions |
@micbar
|
Manger/Co Owner/Uploader/Editor
What is the response of api call https://owncloud.dev/libre-graph-api/#/drives.permissions/ListPermissions on the two different cases? IMO the test should use the response from api call https://owncloud.dev/libre-graph-api/#/drives.permissions/ListPermissions and check if the allowed roles are possible to apply. |
|
@rhafer seems that our allowed roles are not yet scoped. |
related #6993 |
Seems there are two bugs here:
|
…files It was possible to set the 'CreateContainer', 'Move' or 'Delete' permissions on file resources with a CreateShare request. These permissions are meant to be only set on container resources. The UpdateShare request already has a similar check. Partial Fix: owncloud/ocis#8131
Use the condition from the unifiedrole to check if the requested role is actually applicable to the selected resource. Fixes: owncloud#8131
Use the condition from the unifiedrole to check if the requested role is actually applicable to the selected resource. Fixes: owncloud#8131
Use the condition from the unifiedrole to check if the requested role is actually applicable to the selected resource. Fixes: owncloud#8131
Use the condition from the unifiedrole to check if the requested role is actually applicable to the selected resource. Fixes: owncloud#8131
Describe the bug
Creating a share with roles such as Uploader, Viewer, Editor, Manager, or Co-owner is possible. However, when attempting to send an API request to update roles, a "400 Bad Request" error is encountered.
Steps to reproduce
file.txt
with any roles result successful share invitemanager/co-owner/uploader/Editor(for file or folder)
results 400 status codeCases
Expected behavior
We cannot use all roles on all resource types.
The roles have conditions. Some can only be applied to space roots some only to shares.
During share invite, only allowed role should be set
Actual behavior
Can set any role during share invite.
Personal Drive File resource should not allowed to create share invite with role
Co owner/Uploader
Setup
Please describe how you started the server and provide a list of relevant environment variables or configuration files.
OCIS_Version= 5.1.0-prealpha+0f9f996ab
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: