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/23 18:42:00 UTC
[jira] [Updated] (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 updated SLING-11340:
--------------------------------
Description:
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.
was:
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.
> 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
>
>
> 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)