Issue with Adobe Experience Manager integration with PDF Embed API | Community
Skip to main content
joe_s66
October 22, 2021

Issue with Adobe Experience Manager integration with PDF Embed API

  • October 22, 2021
  • 4 replies
  • 2291 views

We have extended the PDF viewer core component in our AEM environments. We have also created API keys for each of the domains in the Adobe Developer Console. When we set up the PDF viewer component in our STAGE author environment, we get the message "This application domain is not authorized to use the provided PDF Embed API Client ID. (please see attached screenshots) The API key is set up to the correct domain.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

4 replies

joe_s66
joe_s66Author
October 22, 2021

We see the following URL getting blocked by Websense on our internal network: https://documentcloud.adobe.com/view-sdk/main.js

We’re using it to connect to Adobe to pass the client API key for the AEM component “PDF Viewer”. Is there a workaround for this issue that anyone could recommend?

Vijayalakshmi_S
October 22, 2021

Hi @joe_s66,

Could you please share the complete markup of the the div with class - cmp-pdfviewer. In particular,  data-cmp-document-path

Also, could you please confirm if all other domains are working fine and the only issue is with stage author ?

Ankur_Khare
Community Advisor
Community Advisor
October 22, 2021

It should work as its working perfectly fine for us across the environments.

joe_s66
joe_s66Author
October 26, 2021

It looks like we need to whitelist the following 4 URI patterns in Forcepoint to resolve the issue. (there are other javascript files besides main.js that the component is dependent on) 

https://documentcloud.adobe.com/dc-core/

https://documentcloud.adobe.com/dc-rendition-provider/

https://documentcloud.adobe.com/dcpreviewdropin/

https://documentcloud.adobe.com/view-sdk/