jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1622) Duplicate configuration services (regression of OAK-1476)
Date Thu, 27 Mar 2014 11:34:17 GMT

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

Chetan Mehrotra commented on OAK-1622:

bq. aim of your original changes was to avoid relying on available of the various services.
so, that would change now and i am not sure if that wouldn't cause regressions.

The aim of the original changes was to ensure that SecurityProvider gets activate donly *after*
the dependent configurations are available. So that would not change with this 

bq.  i'd rather go for the default in the composite cases. this will also be needed once we
have composite authorization setup.

> Duplicate configuration services (regression of OAK-1476)
> ---------------------------------------------------------
>                 Key: OAK-1622
>                 URL: https://issues.apache.org/jira/browse/OAK-1622
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: angela
>            Assignee: angela
>            Priority: Blocker
>             Fix For: 0.20
> [~chetanm], i just was trying to fix an issue with the token configuration options and
found that in the OSGI setup the token and principal configuration service is present twice.
i think this is caused by the changes you made for OAK-1476 introduced a regression with the
principal and token configuration, namely the following lines:
> {code}
> [...]
> compositePrincipalConfiguration.addConfiguration(new PrincipalConfigurationImpl(this));
> [...]
> compositeTokenConfiguration.addConfiguration(new TokenConfigurationImpl(this));
> {code}
> wdyt?

This message was sent by Atlassian JIRA

View raw message