CORS Header issue || AEM Salesforce Integration by leveraging Lighting Out | Community
Skip to main content
Level 2
April 9, 2020
Solved

CORS Header issue || AEM Salesforce Integration by leveraging Lighting Out

  • April 9, 2020
  • 3 replies
  • 8131 views

Hi All,

 

We have made necessary changes in Adobe Cross Origin Sharing Configuration policy in configMgr.

 

Also we have added "Access-Control-Allow-Origin" in headers file under dispatcher.any but we are still facing this below issue. when we try to hit the java script of salesforce component from aem.

 

Access to XMLHttpRequest at 'https://xxxxxxxx.com/c/createClassLightningOut.app?aura.format=JSON&aura.formatAdapter=LIGHTNING_OUT' from origin 'xxAEM DEV AUTHORxxx.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

 

 

 

Thanks,

Sagar

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 shregupt1

This issue was solved through daycare ticket. The issue was at salesforce side and some white-listing was needed to done at their end.

3 replies

Adobe Employee
April 9, 2020

I would recommend checking if the dispatcher is caching the "Access-Control-Allow-Origin" header. Might be an invalid header cached.

 

Also, you can setup a DEBUG logger on "com.adobe.granite.cors" to check for more details about the failure.

 

More troubleshooting steps at [1]

 

[1] https://docs.adobe.com/content/help/en/experience-manager-learn/foundation/security/understand-cross-origin-resource-sharing.html#troubleshooting-cors

Level 2
April 10, 2020
When checked in cors log file no error or issue was detected and also when checked via curl commands we can see the header file present for the domain, but somehow when page is loading that header is not present
arunpatidar
Community Advisor
Community Advisor
April 10, 2020

Hi You have to make CORS changes in salesforce server in order to use their script in your application.

Arun Patidar
shregupt1Adobe EmployeeAccepted solution
Adobe Employee
April 24, 2020

This issue was solved through daycare ticket. The issue was at salesforce side and some white-listing was needed to done at their end.