Hello All,
I need to access AEM Assets from an external application. I saw posts regarding this like I need to use the AssetSelector url (http://localhost:4502/aem/assetpicker) through iFrame tag in the external application.
1. Is this still the correct way to do this?
2. If so, we need to access aem author url only from the external application?
Please provide your pointers.
Thanks,
Parvathy
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
For question 1: Yes, that's how you expose the assets
You can use Asset Selector to expose the assets as a service. Please see below urls for more info:
https://helpx.adobe.com/experience-manager/6-3/assets/using/asset-selector.html
I would recommend to look at the code in the acs-commons and see how they're implementing just to get an idea:
https://adobe-consulting-services.github.io/acs-aem-commons/features/remote-assets/index.html
For Question 2: Depends on the requirement and how you're hosting the servers, you may have to make some more additional code changes plus dispatcher changes to make this work.
Thanks,
Singaiah
Hi,
For question 1: Yes, that's how you expose the assets
You can use Asset Selector to expose the assets as a service. Please see below urls for more info:
https://helpx.adobe.com/experience-manager/6-3/assets/using/asset-selector.html
I would recommend to look at the code in the acs-commons and see how they're implementing just to get an idea:
https://adobe-consulting-services.github.io/acs-aem-commons/features/remote-assets/index.html
For Question 2: Depends on the requirement and how you're hosting the servers, you may have to make some more additional code changes plus dispatcher changes to make this work.
Thanks,
Singaiah
@Parvathy_C
Yeah you can achieve it. Also as @Singaiah_Chintalapudi mentioned it depends on the how you are managing both your server.
May be you also need to update the CORS ORIGIN to allow it on other domain.
Thanks,
Nikhil