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

angela resolved OAK-7018.
-------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.12
                   1.8

[~stillalex], committed revision 1816825.


> 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)

Reply via email to