You may encounter the following exception while enabling the integration between Adobe Target and AEM to share Experience Fragments (XF) and enable Targeting from AEM.
This error can occur even after completing all the steps, including creating a project in the Adobe Developer Console, adding the Adobe Target API with the required profiles, and establishing a successful connection in AEM IMS.
However, when testing the Adobe Target Cloud Services integration, the following exception is thrown:
08.10.2024 12:25:18.280 *ERROR* [[0:0:0:0:0:0:0:1] [1728408318089] POST /libs/cq/analytics/testandtarget/command HTTP/1.1] com.day.cq.analytics.testandtarget.impl.servlets.commands.ConnectCommand Get mboxes request failed!
com.day.cq.analytics.testandtarget.TestandtargetException: Get mboxes request failed!
at com.day.cq.analytics.testandtarget.impl.RestApiAdapter.listMboxes(RestApiAdapter.java:611) [com.adobe.cq.cq-target-integration:1.4.56]
at com.day.cq.analytics.testandtarget.impl.RestApiAdapter.checkCredentials(RestApiAdapter.java:88) [com.adobe.cq.cq-target-integration:1.4.56]
at com.day.cq.analytics.testandtarget.impl.TestandtargetServiceImpl.checkCredentials(TestandtargetServiceImpl.java:180) [com.adobe.cq.cq-target-integration:1.4.56]
at com.day.cq.analytics.testandtarget.impl.servlets.commands.ConnectCommand.performCommand(ConnectCommand.java:83) [com.adobe.cq.cq-target-integration:1.4.56]
at com.day.cq.analytics.testandtarget.impl.servlets.CommandServlet.performCommand(CommandServlet.java:69) [com.adobe.cq.cq-target-integration:1.4.56]
at com.day.cq.commons.servlets.AbstractCommandServlet.doPost(AbstractCommandServlet.java:49) [com.day.cq.cq-commons:5.12.24]
at org.apache.sling.api.servlets.SlingAllMethodsServlet.mayService(SlingAllMethodsServlet.java:146) [org.apache.sling.api:2.27.2]
at org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:342) [org.apache.sling.api:2.27.2]
at org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:374) [org.apache.sling.api:2.27.2]
at org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:551) [org.apache.sling.engine:2.15.14]
Caused by: com.day.cq.analytics.testandtarget.impl.service.WebServiceException: API request failed
at com.day.cq.analytics.testandtarget.impl.service.WebServiceImpl.request(WebServiceImpl.java:646) [com.adobe.cq.cq-target-integration:1.4.56]
at com.day.cq.analytics.testandtarget.impl.service.WebServiceImpl.getMboxes(WebServiceImpl.java:413) [com.adobe.cq.cq-target-integration:1.4.56]
at com.day.cq.analytics.testandtarget.impl.RestApiAdapter.listMboxes(RestApiAdapter.java:600) [com.adobe.cq.cq-target-integration:1.4.56]
... 189 common frames omitted
Caused by: com.day.cq.analytics.testandtarget.impl.service.WebServiceException: Unexpected response status code [403] for request [https://mc.adobe.io/xxxxx/target/mboxes]._{"error_code":"502061","message":"Bad Gateway. No tenant associated with the user profile."}_
at com.day.cq.analytics.testandtarget.impl.service.WebServiceImpl.request(WebServiceImpl.java:643) [com.adobe.cq.cq-target-integration:1.4.56]
... 191 common frames omitted
The issue stems from the Adobe Target Tenant ID not being configured properly. (I will be creating a detailed blog on how to enable the required configurations for integrating AEM with Adobe Target.) It's important to note that the Adobe Target Client Code and Adobe Target Tenant ID are different. The Adobe Target Client Code can be retrieved from the Administration → Implementation section within Adobe Target.
No comments:
Post a Comment