You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/11/03 13:40:00 UTC
[jira] [Updated] (SLING-10906) Implement
ResourceAccessSecurity.can...Value()
[ https://issues.apache.org/jira/browse/SLING-10906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-10906:
------------------------------------
Summary: Implement ResourceAccessSecurity.can...Value() (was: Implement can...Value() )
> Implement ResourceAccessSecurity.can...Value()
> -----------------------------------------------
>
> Key: SLING-10906
> URL: https://issues.apache.org/jira/browse/SLING-10906
> Project: Sling
> Issue Type: Improvement
> Components: Resource Access Security
> Affects Versions: Resource Access Security 1.0.0
> Reporter: Konrad Windszus
> Priority: Major
>
> Currently all methods:
> # {{canReadValue}}
> # {{canSetValue}} and
> # {{canDeleteValue}}
> always return {{false}} in {{ResourceAccessSecurityImpl}}. Although those methods are not used from the resource resolver or any resource provider they should be implemented based on information from the {{ResourceAccessGate}}.
> At the same time the canCreate...Value(s) methods in the {{ResourceAccessGate}} need to be deprecated as there is no dedicated create method for a property in Sling Resource API (both creation and update use the same mechanism).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)