[jira] [Commented] (OAK-6956) RepositoryUpgrade hardcodes SecurityProvider

["Tomek Rękawek (JIRA)" <ji...@apache.org>]

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

Tomek Rękawek commented on OAK-6956:
------------------------------------

[~anchela], as far as I understand, the code using SecurityProviderImpl in RepositoryUpgrade:

1. reads the login and user configuration from the Jackrabbit repository configuration and maps it to the Oak ConfigurationParameters object,
2. basing on the ConfigurationParameters, it creates the SecurityProviderImpl and
3. initializes the repository and workspace with it, creating the whole node structure required by the security code.

Could you provide some hints on how this can be done without the deprecated class during the JCR2->Oak migration?

> 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
>             Fix For: 1.8
>
>
> [~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
(v6.4.14#64029)