Expand my Community achievements bar.

SOLVED

Is it possible to share an DAM asset and can be accessible in the publisher without login

Avatar

Level 2

Hi All, I am looking for an ability to share an asset with someone who hasn’t got a log onto the publisher.

There is one facility to download the asset using email or desktop download, but I need to know about the share asset functionality.

Please suggest your thoughts on it either ootb or new functionality. 

1 Accepted Solution

Avatar

Correct answer by
Administrator

Hi

Please go through the the article mentioned below :-

By default, AEM now prevents read access for anonymous users to certain locations in the repository on a publish server. If the site requests resources in these locations, they will not be loaded and result in a 404 error. We recommend moving these resources to publicly available locations in the repository.

An anonymous web site visitor has no access to following paths in AEM 5.6 or later:

  • /apps
  • /libs
  • /home

It is recommended to place publicly accessible resources in:

  • /content
  • /etc/designs

Link:- https://docs.adobe.com/docs/en/cq/5-6-1/deploying/upgrading/tips-and-troubleshooting.html

 

And there is a community question analogous to you problem:-

Link:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

//

Modify the configuration of Apache Sling Authentication Service.

Add an entry in sling.auth.requirements parameter.

If you want anonymous access, you have to put a '-' before the path.

 

I hope this would help you.

 

Thanks and Regards

Kautuk Sahni



Kautuk Sahni

View solution in original post

5 Replies

Avatar

Level 10

To gain access to a DAM asset without logging in to publish- write a custom sling servlet that returns DAM assets. See https://helpx.adobe.com/experience-manager/using/downloading-dam-assets.html as an example. 

Avatar

Level 2

hi, Thanks for the response but this project is not an implementation project but only managing the assets in the DAM. Please provide any detail if we can configure any properties which allows it to work in this scenario.

Avatar

Level 10

Hi, 

If you open a image of your aem website you will notice path similar to /content/dam/.....

Now what ever path you want to share you can allow that path in dispatcher configuration. but make sure it will be available to public

Avatar

Correct answer by
Administrator

Hi

Please go through the the article mentioned below :-

By default, AEM now prevents read access for anonymous users to certain locations in the repository on a publish server. If the site requests resources in these locations, they will not be loaded and result in a 404 error. We recommend moving these resources to publicly available locations in the repository.

An anonymous web site visitor has no access to following paths in AEM 5.6 or later:

  • /apps
  • /libs
  • /home

It is recommended to place publicly accessible resources in:

  • /content
  • /etc/designs

Link:- https://docs.adobe.com/docs/en/cq/5-6-1/deploying/upgrading/tips-and-troubleshooting.html

 

And there is a community question analogous to you problem:-

Link:- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

//

Modify the configuration of Apache Sling Authentication Service.

Add an entry in sling.auth.requirements parameter.

If you want anonymous access, you have to put a '-' before the path.

 

I hope this would help you.

 

Thanks and Regards

Kautuk Sahni



Kautuk Sahni

Avatar

Employee

Sandeep Rawat wrote...

Hi All, I am looking for an ability to share an asset with someone who hasn’t got a log onto the publisher.

There is one facility to download the asset using email or desktop download, but I need to know about the share asset functionality.

Please suggest your thoughts on it either ootb or new functionality. 

 

Hi Sandeep,

The publish instance allows anonymous access by default, has your publish instance been locked down so no one can access it without first logging in? 

Do you have a author and publish instance? Or is your DAM instance the author and hence locked down by defualt?

If your publish instance has been locked down, then as suggested by Kautuk Sahni you could open a specific path such as "/content/dam/public" and place assets here. On your author instance, your content authors can copy any public assets to this folder and replicate to the publish instance.

If it is an author instance, you can create a servlet or remove authentication requirements from the specific dam folder path. I think the servlet would be more secure as then you can control exactly what is accessible. File type etc.

Regards,

Opkar