[
https://issues.apache.org/jira/browse/OAK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755214#comment-16755214
]
angela commented on OAK-7994:
-----------------------------
[~stillalex],
- jackrabbit api: i agree that it's reasonable to think about the improvement
in terms of feasibility in oak first and only update the jackrabbit API when we
have a better understanding of the changes needed
- ordering: do you mean ascending/descending by principal name or something
else?
- everyone: i wouldn't bother about the everyone principal and 'manually'
inject it but rather marks that as known limitation and hint that
{{PrincipalManager.getEveryone()}} needs to be called if the everyone principal
is not 'native' of a given implementation (e.g. in the default implementation
that would mean if no 'Group' exists, the query won't find/inject it.
- composite: jup.... will think about it.
- different impls: i can help you with that if you wish.... on the bright side
it may help us avoid tailoring it for a specific implementation.
> Principal Management APIs don't allow for search pagination
> -----------------------------------------------------------
>
> Key: OAK-7994
> URL: https://issues.apache.org/jira/browse/OAK-7994
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: security, security-spi
> Reporter: Alex Deparvu
> Assignee: Alex Deparvu
> Priority: Major
>
> Current apis are limited to passing a search token, I'd like to also add
> range (offset, limit).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
