Integration with unusual domain

Report · Jul 07, 2022

Hi all,

I'm trying to use the Adobe Embed API within a native iOS app, and have nearly been successful. I can get the PDF to open, very briefly, before getting the error message:

"The application domain (outsystems://personal-3483432h.outsystemscloud.com) is not authorized to use the provided PDF Embed API Client ID"

I understand what this means. The problem is that, "personal-3483432h.outsystemscloud.com" is listed as my authorised domain in the credentials page. And it seems to fail because it doesn't have the outsystems:// prefix. When I try and add it, the adobe interface won't let me save it because it says the domain is invalid (understandable).

I'm not sure why, but everything that runs on iOS from this outsystems platform has the prefix https:// replaced with outsystems://, and for example, we have to alter content security policies etc to reflect this.

Is there a workaround for this, please?

Thank you

Report · Jul 10, 2022

Hi @Leigh22246404re4z ,

I'm not an expert in Outsystems Cloud but usually the reason that a system would replace "https://" with "outsystems://" or some other URL schema is that a mobile app wants to launch that app when that URL is triggered. Apple's documentation is here.

It could be the case if you are rendering inside of a WebView in the Outsystems app it is also possible that apps will utilize that custom schema as the URL in the WebView which then communicates that as the location to PDF Embed API. I'm not exactly sure what workaround we would have as I think that is more of a behavior of the Outsystems app.