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 "angela (JIRA)" <ji...@apache.org> on 2018/03/19 14:47:00 UTC

[jira] [Updated] (OAK-7356) CugConfiguration may not pick up CugExclude

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

angela updated OAK-7356:
------------------------
    Attachment: OAK-7356.patch

> CugConfiguration may not pick up CugExclude
> -------------------------------------------
>
>                 Key: OAK-7356
>                 URL: https://issues.apache.org/jira/browse/OAK-7356
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: authorization-cug
>            Reporter: angela
>            Assignee: angela
>            Priority: Major
>         Attachments: OAK-7356.patch
>
>
> It seems that the {{CugConfiguration}} may under some circumstances not properly pick up the {{CugExclude}}, which results in the {{CugConfiguration}} falling back to the default, that only excludes the {{AdminPrincipal}}, {{SystemPrincipal}} and {{SystemUserPrincipals}} from CUG evaluation.
> In order to address the issue without disrupting the default setup, I would like to propose the following changes:
> - {{CugConfiguration}}: Change reference cardinality of the the {{CugExclude}} from {{ReferenceCardinality.OPTIONAL_UNARY}} to {{ReferenceCardinality.MANDATORY_UNARY}}
> - {{CugExcludeImpl}}: Don't require an explicit configuration (i.e. drop {{ConfigurationPolicy.REQUIRE}}). Since it extends from {{CugExclude.Default}} the default behavior in absense of a configured set of principal names will be equivalent to the intended default in {{CugConfiguration}} with the optional reference.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)