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

Posted to dev@sling.apache.org by "Eric Norman (Jira)" <ji...@apache.org> on 2022/05/29 20:56:00 UTC

[jira] [Resolved] (SLING-11340) Custom restriction fails validation during modifyAce call

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

Eric Norman resolved SLING-11340.
---------------------------------
    Resolution: Fixed

Merged PR #14 at:  [{{6be4f17}}|https://github.com/apache/sling-org-apache-sling-jcr-jackrabbit-accessmanager/commit/6be4f1712eca50d4cc5ea1514efbd1fd7e98cb6d]

> Custom restriction fails validation during modifyAce call
> ---------------------------------------------------------
>
>                 Key: SLING-11340
>                 URL: https://issues.apache.org/jira/browse/SLING-11340
>             Project: Sling
>          Issue Type: Bug
>            Reporter: Eric Norman
>            Assignee: Eric Norman
>            Priority: Major
>             Fix For: JCR Jackrabbit Access Manager 3.1.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The validation that is checking the posted restriction name is failing for any custom restriction.  (for example from [sling-oak-restrictions|https://sling.apache.org/documentation/bundles/sling-oak-restrictions.html])
> This is happening because the ModifyAce (and related) code is only binding to a single RestrictionProvider component.  There may be multiple RestrictionProvider components available, so the validation should be checking them all for a match.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)