[jboss-jira] [JBoss JIRA] Commented: (JBRULES-428) Access Control List - each node to be protected

[Michael Neale (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBRULES-428?page=comments#action_12341332 ] 
            
Michael Neale commented on JBRULES-428:
---------------------------------------

NOTE: reading the JCR spec, you can assign permissions to individual nodes, so I guess we should use that, then the JCR container will enforce it. Also, the query API will also respect it. If this is that case, it would be better to use the out of the box stuff then re-implementing it. Refer to 6.6.1.2 of the JCR spec, and also 6.9.

Some custom work may need to be done to setup the credentials mapping.

> Access Control List  - each node to be protected
> ------------------------------------------------
>
>                 Key: JBRULES-428
>                 URL: http://jira.jboss.com/jira/browse/JBRULES-428
>             Project: JBoss Rules
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: drools-brms
>            Reporter: Michael Neale
>         Assigned To: Michael Neale
>
> Rule nodes (at least) need to have an ACL: what groups can access it in what capacity. First need to have a structure for ACLs to be stored.
> They should be tied to user groups/roles, not individual logins. 
> JAAS should provide the user name and the users context (group membership) I believe. 
> When there is an ACL, it must be checked to see if the user (via their group membership) can do one of the following:
> Edit, change status, view, delete. 
> If they can't view, ideally it will not be shown in any "lists", but if that is not feasable, it would be acceptable to list it, but not show the contents. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira