jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomek Rękawek (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-6956) RepositoryUpgrade hardcodes SecurityProvider
Date Thu, 21 Dec 2017 08:39:00 GMT

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

Tomek Rękawek commented on OAK-6956:

Since I wasn't able to find an alternative to SecurityProviderImpl, I'll reschedule it and
re-assign back to Angela.

[~anchela] - I'll be happy to replace the SecurityProviderImpl if we find a way to instantiate
another SecurityProvider implementation within the oak-upgrade runtime.

> RepositoryUpgrade hardcodes SecurityProvider
> --------------------------------------------
>                 Key: OAK-6956
>                 URL: https://issues.apache.org/jira/browse/OAK-6956
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: upgrade
>            Reporter: angela
>            Assignee: Tomek Rękawek
>            Priority: Critical
> [~tomek.rekawek] Looking at non-test usage of the (to be deprecated) {{SecurityProviderImpl}}
I noticed one usage in the {{RepositoryUpgrade}} that looks troublesome to me.
> I would strongly recommend to fix that given the fact that we no longer use {{SecurityProviderImpl}}
in production ready setup scenarios.
> cc: [~stillalex]

This message was sent by Atlassian JIRA

View raw message