-
Notifications
You must be signed in to change notification settings - Fork 187
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
[Sharing NG] Link password capabilities are not being respected on update #8725
Comments
There is a special case: some users can leave the password out when updating. |
Story: #7538 |
@JammingBen Can we close this? Please check if you can follow my understanding of the expected behavior. @AlexAndBear Was implementing that. |
Alex implemented this in Web. But the API still allows to change the role, therefore ignoring the capabilities. IMO that should be fixed. |
This was fixed with cs3org/reva#4622 |
Describe the bug
The capabilities for link passwords are not being respected on update.
Steps to reproduce
internal
, which will remove the password because internal links don't have a passwordedit
without setting a new password (PATCH
to e.g.https://host.docker.internal:9200/graph/v1beta1/drives/e310554b-25a9-4f97-a423-8b1ff5d77254%24ff10588e-0c68-46c1-a984-c859f8fbdd20/items/e310554b-25a9-4f97-a423-8b1ff5d77254%24ff10588e-0c68-46c1-a984-c859f8fbdd20\u0021c984993a-d361-45a1-b829-9231ee827c81/permissions/tSclcXHFrIvAnaB
)Expected behavior
The server should throw an error like "passwords are enforced".
Actual behavior
The link is being updated sucsessfully.
Note that there are some edge cases to this scenario. I don't remember the details, but if I'm not mistaken, admins can remove an existing password for the
view
role despite passwords being enforced. So in the example above, changing the type toview
should still be possible without password (for admins). Maybe @micbar or @tbsbdr can confirm this.The text was updated successfully, but these errors were encountered: