Sign in to Community
Sign in to view all badges
I am working on solution for enterprise DAM wherein I need to provide read only access to all DAM Assets on publish.
Why can't I directly expose expose DAM/Assets console on Publish server to the end user by enabling it through dispatcher?
Why do I need to user solutions like "Asset Share Commons" or "Create custom asset view" or "Brand portal(might be a overkill)" for this.
You earliest possible answer to this would be very help. Thanks.
Well depends on your use case. If the console is used by internal users (behind a firewall) - it could be good enough. I would not use it to expose assets to the public (on Internet).
Its not written anywhere but the very reason of development of AEM asset share commons or brand portal is being given as that we should not expose publish Assets console in Enterprise DAM solution.
Technically exposing Publish Assets console is a possible solution. But would it be a good solution. That is the question.
Hi mozzvinod - I just wonder - where do you read that you "can't I directly expose expose DAM/Assets console on Publish server to the end user by enabling it through dispatcher?"