[
https://issues.apache.org/jira/browse/OAK-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Aggarwal updated OAK-1976:
--------------------------------
Description:
Our own custom principalConfiguration service is not getting registered with
SecurityProvider.
Adding ' policy = ReferencePolicy.DYNAMIC ' in the attributes of the
CompositePrincipalConfiguration reference of class
org.apache.jackrabbit.oak.security.SecurityProviderImpl
solved the issue.
was:
On adding our own custom principalConfiguration to
CompositePrincipalConfiguration in SecurityProvider, it seems that it is not
able to add it to the list of principalProviders.
Adding ' policy = ReferencePolicy.DYNAMIC ' in the attributes of the
CompositePrincipalConfiguration reference of class
org.apache.jackrabbit.oak.security.SecurityProviderImpl
solved the issue.
> SecurityProvider is not able to add Custom PrincipalConfiguration in
> CompositePrincipalConfiguration in OSGI Mode
> -----------------------------------------------------------------------------------------------------------------
>
> Key: OAK-1976
> URL: https://issues.apache.org/jira/browse/OAK-1976
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0
> Reporter: Ankit Aggarwal
> Priority: Minor
>
> Our own custom principalConfiguration service is not getting registered with
> SecurityProvider.
> Adding ' policy = ReferencePolicy.DYNAMIC ' in the attributes of the
> CompositePrincipalConfiguration reference of class
> org.apache.jackrabbit.oak.security.SecurityProviderImpl
> solved the issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
