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 "angela (JIRA)" <ji...@apache.org> on 2015/03/27 15:00:54 UTC
[jira] [Created] (OAK-2690) Add optional
UserConfiguration#getUserPrincipalProvider()
angela created OAK-2690:
---------------------------
Summary: Add optional UserConfiguration#getUserPrincipalProvider()
Key: OAK-2690
URL: https://issues.apache.org/jira/browse/OAK-2690
Project: Jackrabbit Oak
Issue Type: Improvement
Components: core
Reporter: angela
while playing around with overall group principal resolution during the repository login, I thought that having a principal provider that knows about the details of the user management implementation may might be a slight improvement compared to the generic default implementation as present in {{org.apache.jackrabbit.oak.security.principal.PrincipalProviderImpl}}, which just acts on the {{UserManager}} interface and thus always creates intermediate {{Authorizable}} objects.
in order to be able to get there (without having the default principal mgt implementation rely on implementation details of the user mgt module), we would need an addition to the {{UserConfiguration}} that allows to optionally obtain a {{PrincipalProvider}}; the fallback in the default {{PrincipalConfiguration}} in case the user configuration does not expose a specific principal provider would be the current (generic) solution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)