You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2013/06/04 19:03:20 UTC

[jira] [Commented] (OAK-527) Implement Permission evaluation

    [ https://issues.apache.org/jira/browse/OAK-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674566#comment-13674566 ] 

angela commented on OAK-527:
----------------------------

Revision: 1489515
changed permission store to contain a hierarchical view of the entries for a single principal instead of
keeping a flat, unstructured list. this allow to read permission entries lazily or partially depending on
the number and structure of policy nodes and entries in the content.
                
> Implement Permission evaluation
> -------------------------------
>
>                 Key: OAK-527
>                 URL: https://issues.apache.org/jira/browse/OAK-527
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: core, jcr
>            Reporter: angela
>            Assignee: angela
>
> this subtasks goes along with OAK-526: for efficient permission
> evaluation the compiledpermission implementation should not attempt
> to collect the relevant ac-content such as looked at and written by
> the jcr ac-mgt implementation. instead it should make use of the
> persisted effective permission for the dedicated set of principals
> that forms the subject of a given contentsession.
> tbd:
> - privileged access to the effective permission store (independent of
>   the content sessions permission)
> - ability to read all required information from the target tree/property
>   that is passed to the hasPermission/canRead call.
> - efficient handling of pluggable restrictions
> - special handling for access control content an items residing inside 
>   the version store.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira