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 2014/02/27 09:56:21 UTC

[jira] [Commented] (OAK-1476) Hardcoded SecurityProvider implementation in oak-jcr Activator

    [ https://issues.apache.org/jira/browse/OAK-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914232#comment-13914232 ] 

angela commented on OAK-1476:
-----------------------------

in addition the buildSecurityConfig method add some adobe specific default values for the user mgt setup. what's the intention behind this?

> 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: Jukka Zitting
>             Fix For: 0.19
>
>
> 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.1.5#6160)