[
https://issues.apache.org/jira/browse/OAK-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-1476:
---------------------------------
Attachment: OAK-1476-2.patch
Updated patch which incorporates feedback from Tobi
Key aspects
* SecurityProvider now has required dependencies to all the security
configuration components
* If any config needs to be tweaked from default then it should be provisioned
before Oak related bundles are started.
* Moved the logic from Activator to RepositoryManager and made it to require
configuration. This would allow users to use the default setup and also give
them the choice to disable default setup and configure repository in custom mode
> 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-2.patch, 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)
