Hi everyone
I found an issue on ACS while getting emails created on AEM6.2 On-Premise.
This is what I did:
I created correctly the AEM template inside ACS as described in the official Documentation
https%3A%2F%2(tenant name hidden)-mkt-stage1.campaign.adobe.com%2Frest%2Fhead%2Fdelivery%2F%2540n3QzGAFa4MzxBlkO9ZJxrbX5zGNRBGC0trLYTZ1luMG0U_IysGbAEhJ-GNe6z-_Yitj9SqRQDnNWZraNcvi1wx-NvL0%2FaemContents%2F%3FlabelFilter%3D%26approvedFilter%3Dtrue%26linkedFilter%3Dfalse%26_order%3DlastModified%2520desc%26_lineStart%3D0%26_lineCount%3D30
The answer is:
XTK-170019 Access denied.
SOP-330011 Error while executing the method 'GetAEMContentList' of service 'nms:delivery'.
XTK-170006 Unable to parse expression 'GetAEMContentList($(labelFilter) , $(approvedFilter) , $(linkedFilter) , $(_order) , $(_lineCount) , $(_lineStart))'.
XTK-170006 Unable to parse expression 'GetAEMContentList($(labelFilter) , $(approvedFilter) , $(linkedFilter) , $(_order) , $(_lineCount) , $(_lineStart))'.
- Inspecting the AEM6.2 author error.log we got the following GET request:
10.10.2017 12:36:38.396 *INFO* [52.213.132.36 [1507631798395] GET /api/content/sites/campaigns.json HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /api/content/sites/campaigns.json not found
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
after a deep analysis the problem was on dispatcher level.
The problem occurred by missing authorization value declaration from the /clientheaders dispatcher section.
Hi,
I've the same setup and ACS can get the template list from AEM successfully.
Have you modified the permissions of the campaign-remote user? By default it should have access to /content/campaigns. Does this path exist on your AEM instance? Pulling in email templates is possible from this path only. The /content/campaigns path is hard-coded, and only the resource types of your email templates can be configured on ACS side.
Views
Replies
Total Likes
Hi,
after a deep analysis the problem was on dispatcher level.
The problem occurred by missing authorization value declaration from the /clientheaders dispatcher section.
i found the same error even after doing everything mentioned. can you please let me know authorization value you added for the integration to work.
should i white-list something.
Thank You!
Views
Replies
Total Likes
Views
Likes
Replies