Restrict the upload of unlicensed material and PII violations in AEM Assets | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by EstebanBustamante

Unfortunately, I believe the way to determine if an asset is PII compliant would be through its metadata, which becomes available through the AEM APIs once the asset is processed/uploaded. You could consider overlaying the upload functionality to check the metadata and determine if the asset is allowed to be stored, as there are no pre-processors available. Alternatively, you could think about adding post-processors to delete the asset after it has been uploaded and identified as forbidden, using a method like this: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/manage/asset-microservices-configure-and-use.html?lang=en#post-processing-workflows 

 

2 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
October 6, 2023

Unfortunately, I believe the way to determine if an asset is PII compliant would be through its metadata, which becomes available through the AEM APIs once the asset is processed/uploaded. You could consider overlaying the upload functionality to check the metadata and determine if the asset is allowed to be stored, as there are no pre-processors available. Alternatively, you could think about adding post-processors to delete the asset after it has been uploaded and identified as forbidden, using a method like this: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/assets/manage/asset-microservices-configure-and-use.html?lang=en#post-processing-workflows 

 

Esteban Bustamante
arunpatidar
Community Advisor
Community Advisor
October 9, 2023

Agree with @estebanbustamante ,

You have the option to send an email notification when a license is no longer valid, either because it is unlicensed or has expired. To accomplish this, you can set up a daily scheduler to monitor the status of licenses. For instance, you can send email notifications:

- One day before the license expires.
- Seven days before expiration.
- Fourteen days before expiration.

Additionally, if a license has expired, you can automatically unpublish the associated assets and add relevant metadata for reporting purposes in the notification email.

Arun Patidar