For our customer, when trying to use the PDF Embed API [https://www.adobe.io/apis/documentcloud/dcsdk/] it appears that the following URL is getting blocked on their internal network and impacting the PDF Viewer from passing the client API key --> https://documentcloud.adobe.com/view-sdk/main.js
Is there a workaround to preventing this URL from getting blocked for internal firewalls?
Furthermore, there are 4 URI patterns for https://documentcloud.adobe.com used in https://www.aemcomponents.dev/content/core-components-examples/library/page-authoring/pdf-viewer.htm... .
The short answer is no. I'd see if they can whitelist these URLs for their firewall.
At this time - sorry no.
So you basically saying that Adobe doesn't care the many of its largest customers that use Forcepoint security sofware are blocked from using the PDF embed API code?
We are aware that some orgs can't use the API due to the URL being blocked. We _absolutely_ care. For now though there is not a workaround unless you can whitelist the specific URLs.
Is it possible to download adobe's js files to self host them on our own servers?
Did anyone find a work around for this? We are running into the same issue.
Have you tried with the latest version hosted on documentservices.adobe.com?
Thank you Raymond for responding. No we are using the view sdk from documentcloud.adobe.com. Do you think using documentservices.adobe.com would solve the problem? whats the difference between documentcloud and document services?
documentservices.adobe.com is not blocked quite as heavily. Try out the online demo in your environment and see if it works for you.