[SLING-10906] Implement ResourceAccessSecurity.can...Value()

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Resource Access Security 1.0.0
• Component/s: Resource Access Security
• Assignee: Unassigned
• Reporter: Konrad Windszus
• Created: 03/Nov/21 13:39
• Updated: 03/Nov/21 18:15

Description

Currently all methods:

1. canReadValue
2. canSetValue and
3. 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).
The canReadValue must also be evaluated before inside ResourceAccessSecurityImpl.getReadableResource() to only expose a subset of properties.