jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (OAK-8151) Let ACE.getPrincipal return principals obtained from PrincipalManager
Date Wed, 20 Mar 2019 15:03:00 GMT

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

angela reassigned OAK-8151:
---------------------------

    Assignee: angela

> Let ACE.getPrincipal return principals obtained from PrincipalManager
> ---------------------------------------------------------------------
>
>                 Key: OAK-8151
>                 URL: https://issues.apache.org/jira/browse/OAK-8151
>             Project: Jackrabbit Oak
>          Issue Type: Wish
>          Components: core, security
>            Reporter: angela
>            Assignee: angela
>            Priority: Minor
>         Attachments: OAK-8151.patch
>
>
> [~stillalex], while {{AccessControlEntry.getPrincipal}} does not mandate the that principal
is actually obtained from {{PrincipalManager}} it turned out that some UI code actually relies
on that implementation detail. 
> we could still reduce the number of queries resulting from looking up principals by name,
by making sure we don't read the same principal multiple times, while computing the entries
for a given access control list. that might be somewhat of a compromise to reduce the number
of lookups while returning the same principals as we did before optimizing the lookup in OAK-7880.



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

Mime
View raw message