You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2016/10/26 12:18:58 UTC

[jira] [Commented] (JCRVLT-111) Add support for o.a.j.api.security.authorization.PrincipalSetPolicy

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

angela commented on JCRVLT-111:
-------------------------------

sure... to be honest, I originally planned to provide tests with decent coverage but I found myself struggling with the tests present and feared that i would spend way to much time on this. if you can provide me with some instructions or explanation on how test-coverage in jackrabbit filevault is organized I will be happy to provide tests.

> Add support for o.a.j.api.security.authorization.PrincipalSetPolicy
> -------------------------------------------------------------------
>
>                 Key: JCRVLT-111
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-111
>             Project: Jackrabbit FileVault
>          Issue Type: New Feature
>            Reporter: angela
>            Assignee: Tobias Bocanegra
>             Fix For: 3.1.30
>
>         Attachments: JCRVLT-111.patch
>
>
> jackrabbit API has been extended by an additional type of access control policy, which isn't an ACL. fvault should be adjusted to be able to properly import that type of access control policy.
> as discussed: ac-handling {{MERGE}} and {{MERGE_PRESERVE}} should be implemented the same way and just add extra principal names that are not yet present in the set.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)