• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Issue with Adobe Experience Manager integration with PDF Embed API

Explorer ,
Oct 22, 2021 Oct 22, 2021

Copy link to clipboard

Copied

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.

pdfviewer-screenshot1.pngpdfviewer-screenshot2.png

Views

354

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Explorer , Oct 26, 2021 Oct 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/

Votes

Translate

Translate
Explorer ,
Oct 22, 2021 Oct 22, 2021

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 25, 2021 Oct 25, 2021

Copy link to clipboard

Copied

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?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 26, 2021 Oct 26, 2021

Copy link to clipboard

Copied

LATEST

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/

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources