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] [Created] (OAK-7018) Move setup of composite security configurations to SecurityProviderBuilder
Date Fri, 01 Dec 2017 10:47:00 GMT
angela created OAK-7018:
---------------------------

             Summary: 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


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

Mime
View raw message