-
Type: User story
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.6.0-HF27, 5.8.0-HF02, 5.9.1
-
Component/s: Nuxeo Drive
-
Backlog priority:900
Handle permission updates server side, typically grant Read <=> creation, deny Read <=> deletion
Currently the permission updates server side are not detected by the audit change finder.
Thus several cases are not dealt with, for example:
- Denying Read access on a document should mark the file/folder as 'unsynchronized' in the local DB if it has been locally modified since last synchronized (to keep the local changes), else delete it. Currently the file/folder stays in the client hierarchy and the last known states table, therefore any operation on it will crash, typically in the case of a folder trying to create a child file.
- Granting Read access on a document should be considered by the client either as:
- A creation if it doesn't exist locally.
- A match with a file system item existing locally
- depends on
-
NXP-11469 DENY Read Permission on synchronized documents should not be detected as invalid credentials by the client
- Resolved
-
NXP-11146 Invalidate synchronization roots cache if ACL change
- Resolved
- is required by
-
NXP-13088 As a User, when I delete on the server, a file that has been modified offline by another user, what happens
- Resolved