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
While the ocis server should not send the R (re-sharing) permission for items in the Shares Jail, I've been told that it's not entirely impossible, either - and that therefore the client should take measures beyond interpreting the returned permissions to no longer offer sharing for a file shared with the user.
Technically, this could be solved with OCItem not returning the re-sharing permission bit through its properties if it determines it is located in the Shares Jail. This, however, would come at a performance cost whenever permissions are checked for an OCItem.
A more efficient solution, then, is to take advantage of the Action subsystem's ability to let actions themselves control for which items they want to appear - and in which location.
The CollaborateAction (which is responsible for sharing) then can simply check the Drive ID (Space ID) of the OCItem to determine if the item is located in the Shares Jail. If it is OCDriveIDSharesJail (a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668), the item is located in the Shares Jail and Sharing options should no longer be presented for the item.
The text was updated successfully, but these errors were encountered:
Re-sharing has been removed from ocis and ocis-web:
While the ocis server should not send the
R
(re-sharing) permission for items in the Shares Jail, I've been told that it's not entirely impossible, either - and that therefore the client should take measures beyond interpreting the returned permissions to no longer offer sharing for a file shared with the user.Technically, this could be solved with
OCItem
not returning the re-sharing permission bit through its properties if it determines it is located in the Shares Jail. This, however, would come at a performance cost whenever permissions are checked for anOCItem
.A more efficient solution, then, is to take advantage of the
Action
subsystem's ability to let actions themselves control for which items they want to appear - and in which location.The
CollaborateAction
(which is responsible for sharing) then can simply check the Drive ID (Space ID) of theOCItem
to determine if the item is located in the Shares Jail. If it isOCDriveIDSharesJail
(a0ca6a90-a365-4782-871e-d44447bbc668$a0ca6a90-a365-4782-871e-d44447bbc668
), the item is located in the Shares Jail and Sharing options should no longer be presented for the item.The text was updated successfully, but these errors were encountered: