[
https://issues.apache.org/jira/browse/OAK-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949032#comment-13949032
]
angela commented on OAK-1622:
-----------------------------
making this a blocker as with the current setup it will prevents the
corresponding OSGI configuration (e.g. token expiration) from taking effect.
as a short term fix with minimal risk i will change the setup such that
composite will have a default value instead of populating the internal
collection of services.
> 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: Chetan Mehrotra
> 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
(v6.2#6252)
