jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1005) More Fine grained Permission Flags
Date Wed, 15 Aug 2007 14:51:30 GMT

    [ https://issues.apache.org/jira/browse/JCR-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519984

Stefan Guggisberg commented on JCR-1005:

> there is my problem. In my scenario the user trys to add a new node (File->Save As)
on a parent node and i should now
> if he try to save the original file or if he try to save the file with a other name ....

if the user saves the original file the parent node shouldn't be modified; OTOH if he saves
the file with a new name the parent node will be modified.

> More Fine grained Permission Flags
> ----------------------------------
>                 Key: JCR-1005
>                 URL: https://issues.apache.org/jira/browse/JCR-1005
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 1.3
>            Reporter: Claus Köll
>         Attachments: acces.patch
> It would be fine to have one more Permission Flag on node add.
> At the moment there are 3 flags. We need to know if a node will be updated or created.
> This is not possible with the current implementation because on node add the permission
> AccessManager.WRITE will be used. This is a Problem in a  WebDav Scenario with Microsoft-Word
because if i open a Node and 
> try to save it i need write permissions on the parent node. this is ok. If a user trys
to save the file with a other name
> he can because the same PermissionFlag will be used.
> Maybe there is a other solution for this problem ?
> BR,
> claus

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message