Exposing DAM/Assets console on Publish server. | Community
Skip to main content
mozzvinod
mozzvinod
Level 2
June 10, 2019
Solved

Exposing DAM/Assets console on Publish server.

  • June 10, 2019
  • 3 replies
  • 4272 views

Hi All,

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.

Regards,

Vinod

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 KrassimirBo

Hi Vinod,

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).

Best,

Krassimir

KBWEB

3 replies

K
KrassimirBo
Level 3
June 14, 2019

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?"

Thanks,

Krassimir

mozzvinod
mozzvinodAuthor
Level 2
July 2, 2019

Hi KBWEB​

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.

Regards,

Vinod

K
KrassimirBoAccepted solution
Level 3
July 3, 2019

Hi Vinod,

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).

Best,

Krassimir

KBWEB

Terms & ConditionsAccessibility statement

Loading footer...