Skip to main content
joe_s66
joe_s66
Participant
October 22, 2021
Answered

Issue with Adobe Experience Manager integration with PDF Embed API

  • October 22, 2021
  • 1 reply
  • 620 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 topic has been closed for replies.
    Correct answer joe_s66

    It looks like we need to whitelist the following path in Forcepoint to resolve the issue. (there are other javascript files besides main.js that the component is dependent on) https://documentcloud.adobe.com/view-sdk/

    1 reply

    joe_s66
    joe_s66Author
    Participant
    October 22, 2021

    I fixed the issue by generating a new API key. I'm still unclear why the first one didn't work with the allowed domain.

    joe_s66
    joe_s66Author
    Participant
    October 25, 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?

    joe_s66
    joe_s66AuthorCorrect answer
    Participant
    October 26, 2021

    It looks like we need to whitelist the following path in Forcepoint to resolve the issue. (there are other javascript files besides main.js that the component is dependent on) https://documentcloud.adobe.com/view-sdk/

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices