[ 
https://issues.apache.org/jira/browse/OAK-7880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Davide Giannella updated OAK-7880:
----------------------------------
    Fix Version/s:     (was: 1.10)
                   1.10.0

> Reduce Principal lookup in default access control code base
> -----------------------------------------------------------
>
>                 Key: OAK-7880
>                 URL: https://issues.apache.org/jira/browse/OAK-7880
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: angela
>            Assignee: angela
>            Priority: Minor
>             Fix For: 1.10.0, 1.9.11
>
>         Attachments: OAK-7880.patch
>
>
> today i spotted to places in {{AccessControlManagerImpl}}, where i think the 
> principal lookup could be omitted altogether:
> {{a) AccessControlManagerImpl.getPrincipal(Tree)}} : called when building 
> policies from the content -> principal is always created even if not known.
> b)  {{Util.checkValidPrincipal(Principal, PrincipalManager, int)}} : in case 
> of ImportBehavior.BESTEFFORT the result of the lookup is ignored and the 
> lookup could in this case be omitted.
> [~stillalex], what do you think? If you feel this is worth addressing, I 
> would create a patch.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to