[
https://issues.apache.org/jira/browse/OAK-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924155#comment-13924155
]
Tobias Bocanegra commented on OAK-1476:
---------------------------------------
I don't think that is correct using OPTIONAL references in the security
provider. The problem is, that the initial configurations set in the
constructor) are only used in the non-osgi case. The SecurityProvider must not
be available before all its configs are. otherwise the repository might start
too early with the wrong config.
Ultimately, I think we should get rid of the SecurityProvider, as it currently
only acts merely as service registry for the security bits.
> Hardcoded SecurityProvider implementation in oak-jcr Activator
> --------------------------------------------------------------
>
> Key: OAK-1476
> URL: https://issues.apache.org/jira/browse/OAK-1476
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: angela
> Assignee: Chetan Mehrotra
> Fix For: 0.20
>
> Attachments: OAK-1476.patch
>
>
> the Activator in o.a.j.oak.jcr.jcr.osgi contains a hardcoded reference to the
> SecurityProviderImpl. This is obviously not the desired outcome of making the
> security part pluggable at runtime.
> [~jukkaz], since you are the author of the Activator, could you take a look
> at this again?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
