cancel
Showing results for 
Search instead for 
Did you mean: 

"SAP BTP Launchpad" with "SAP S/4HANA on-premise" as content provider use local backend URL

SamueleBarzaghi
Participant
0 Kudos

Hello,

We are currently using SAP Build Workzone, standard edition (BTP Launchpad), and are utilizing an on-premise S/4HANA system as our content provider.

We have published several apps, and while the dynamic tiles are working correctly (the OData calls to the backend to retrieve the count are correct), we are encountering an issue when attempting to launch the apps. Specifically, the iframe is using the local hostname of the S/4HANA backend instead of the BTP destination.

We have encountered this exact issue:

https://answers.sap.com/questions/13218366/pointing-sap-ui5-app-on-prem-in-sap-fiori-cloud-er.html?c...

20:15:59.226 login [INFO] Starting login controller
<id>-sapdelim-<destination>.launchpad.cfapps.eu10.hana.ondemand.com/sap/public/bc/ui2/logon/fiori3/js/redirect.js:942 

20:15:59.227 login [INFO] Starting login controller
<id>-sapdelim-<destination>.launchpad.cfapps.eu10.hana.ondemand.com/sap/public/bc/ui2/logon/fiori3/js/redirect.js:942  

20:15:59.227 login [INFO] Navigating to https://<onprem url>/sap/bc/ui2/flp/ui5appruntime.html?sap-ui-app-id=snt.zcon.create1&sap-startup-params=dokar%3dCON&sap-shell=FLP&sap-touch=0&sap-ui-versionedLibCss=true&sap-theme=zentiva_fiori3%40https%3a%2f%2fzaws.launchpad.cfapps.eu10.hana.ondemand.com%2fcomsapuitheming.runtime%2fthemeroot%2fv1&sap-iframe-hint=UI5
zaws-sapdelim-testcnrbasic.launchpad.cfapps.eu10.hana.ondemand.com/sap/public/bc/ui2/logon/fiori3/js/redirect.js:942 

20:15:59.483 login [INFO] Framing allowed, activating application

Thank you for support

Regards,

Sam

View Entire Topic
SamueleBarzaghi
Participant
0 Kudos

Problem has been resolved.

It turns out that the cloud connector was configured to access the internal host using HTTP instead of HTTPS.

As a result, the first response to the ui5appruntime was redirecting to HTTPS with the internal hostname.

We were able to fix the issue by changing the settings in the cloud connector from HTTP to HTTPS.