jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (Jira)" <j...@apache.org>
Subject [jira] [Commented] (OAK-8151) Let ACE.getPrincipal return principals obtained from PrincipalManager
Date Wed, 04 Dec 2019 11:24:00 GMT

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

Julian Reschke commented on OAK-8151:

trunk: (1.12.0) [r1855986|http://svn.apache.org/r1855986]
1.10: [r1870823|http://svn.apache.org/r1870823] [r1870597|http://svn.apache.org/r1870597]

> 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 Schreiber
>            Assignee: Angela Schreiber
>            Priority: Minor
>             Fix For: 1.12.0
>         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

View raw message