You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Alex Deparvu (JIRA)" <ji...@apache.org> on 2017/12/01 10:55:00 UTC

[jira] [Commented] (OAK-7018) Move setup of composite security configurations to SecurityProviderBuilder

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

Alex Deparvu commented on OAK-7018:
-----------------------------------

looks good!

> Move setup of composite security configurations to SecurityProviderBuilder
> --------------------------------------------------------------------------
>
>                 Key: OAK-7018
>                 URL: https://issues.apache.org/jira/browse/OAK-7018
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: auth-external, authorization-cug, core
>            Reporter: angela
>            Assignee: angela
>             Fix For: 1.8, 1.7.12
>
>
> [~stillalex], while working on OAK-7010 I noticed that tests in _oak-auth-external_ and _oak-authorization-cug_ use a similar way to plug additional security configurations into the {{SecurityProvider}}. Now that we have the _SecurityProviderBuilder_ I think that we might be able to avoid that 'duplication' by adding another method to the builder and setup the composite configurations when creating the {{SecurityProvider}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)