Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

AEM - Restrict DAM Asset Activation to Publish Instance | AEM Community Blog Seeding

Avatar

Administrator

BlogImage.jpg

AEM - Restrict DAM Asset Activation to Publish Instance by Bimmisoi Blog

Abstract

As now a days we use dynamic media so we do not need assets on publish environment.

In order to restrict the DAM asset activation we have done following steps:
1. Create a user on every environment's author instance with full access excluding access on /content/dam/. For now we have created a user named replication-user.
2. Go to replication agent of the author
3. Click on edit, on the model window add the name of the user created in Agent User ID field and click on ok.
4. Now when you publish any asset under/content/dam/ it will not be replicated to the publish instance from the author environment.

Read Full Blog

AEM - Restrict DAM Asset Activation to Publish Instance

Q&A

Please use this thread to ask the related questions.



Kautuk Sahni
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Reply

Avatar

Community Advisor

@kautuk_sahni This will restrict even metadata of the images from publisher right? Is there anyway if we need metadata in publishers but not the assets? Because usually we have lot metadata including title/alttext which is needed to build an image component.

 

Please suggest.