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 "Julian Reschke (Jira)" <ji...@apache.org> on 2019/12/04 11:22:00 UTC
[jira] [Issue Comment Deleted] (OAK-8151) Let ACE.getPrincipal
return principals obtained from PrincipalManager
[ https://issues.apache.org/jira/browse/OAK-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated OAK-8151:
--------------------------------
Comment: was deleted
(was: trunk: (1.12.0) [r1855986|http://svn.apache.org/r1855986])
> 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
(v8.3.4#803005)