jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-3901) SecurityProviderRegistration must respect service ranking of aggregated configurations
Date Thu, 28 Jan 2016 09:46:40 GMT

     [ https://issues.apache.org/jira/browse/OAK-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

angela resolved OAK-3901.
-------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.4)
                   1.3.15

Committed revision 1727293.

Change the {{SecurityProviderRegistration}} to use the same way of collecting multiple configurations
as {{SecurityProviderImpl}} addressing both the OAK-3901 and OAK-3902. Extended the groovy
test and added a java unit test for {{SecurityProviderRegistration}}.

[~frm] thanks a lot for your help and the review. very much appreciated.

> SecurityProviderRegistration must respect service ranking of aggregated configurations
> --------------------------------------------------------------------------------------
>
>                 Key: OAK-3901
>                 URL: https://issues.apache.org/jira/browse/OAK-3901
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: angela
>            Assignee: angela
>            Priority: Critical
>             Fix For: 1.3.15
>
>
> while working on aggregating multiple authorization configurations i spotted that in
contrast to {{SecurityProviderImpl}} the {{SecurityProviderRegistration}} doesn't respect
the service ranking (or the corresponding config option) to define the order of the individual
configurations in the aggregation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message