Asset Metadata Driven Permission

[rAndrijana]

Hi,

I would like to set up metadata driven permissions on Assets so I figured out that OOTB feature should exist based on the documentation

https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/advanced/metadata-driven-....

However when i set up locally (using the latest SDK available) it is not working - I am not able to see the property I configured in the json appearing in my permission section.

Does anyone else have the same issue?

Thanks,

Andrijana

[shubhanshu_singh · Accepted solution]

Hi @rAndrijana ,

You need to restart the local instance or reload bundles after your configuration is deployed. I followed the documentation and faced the same issue locally. On restart, AEM reloads all OSGi bundles and their configurations. This ensures that the service bound to DefaultRestrictionProviderConfiguration picks up the new or modified configuration.

PFB screen capture from my local machine

Local Specification
AEM SDK version: AEM SDK v2024.11.18598.20241113T125352Z-241100

Java : 11.0.25

[rAndrijana]

Thank you very much

[AnushaV2]

Hello,

I'm encountering an issue with metadata-driven permissions in Adobe Experience Manager (AEM). In my local environment, everything functions as expected; however, upon deploying to the development environment, I'm receiving the following error:

Could not process yaml files / e=biz.netcentric.cq.tools.actool.validators.exceptions.InvalidRestrictionsException: Validation error while reading ACE definition nr.62 of authorizable DAM Asset Consumers AEM, this repository doesn't support following restriction(s): [dam:status]
Configuration
{
"restrictionPropertyNames": [
"dam:status"
],
"restrictionContentPropertyNames": [],
"enabled": true
}

Steps Taken:

Verified the existence of the dam:status property in the development environment

Confirmed that the OSGi configuration file is deployed in the development environment.

Could anyone provide insights into why this discrepancy might occur between environments? Any suggestions on further steps to resolve this issue would be greatly appreciated.

[rAndrijana]

Hello,

Can you please share how you configure the restriction in the yaml file?

Regards,

Andrijana