oData Requests from Neo Launchpad App to Foundry CAP node.js

[matteoprinetti]

Hi all,

we have this scenario: we run a NEO Launchpad with on-premise Destinations via Cloud Connector.

Now on Foundry (on the same subaccount) we have a new oData Provider which is based on CAP / node.js. So we need to create a destination on Neo and configure Mutual Trust etc.

We are following this https://help.sap.com/docs/BTP/ea72206b834e4ace9cd834feed6c0e09/6e194f8e919a40bab7e39cd992677cb7.html... (Principal Propagation between Neo and Foundry) BUT:

The java app provided as client example (neo side) fetches the OAuth SAML Bearer from the header, and creates the ssl connection setting this header in the request.

How to do the same with the SAPUi5 HTML app ? Does it happens automatically ?

Specifically the question is: How to connect the NEO HTMl5 App in the Launchpad with the Foundry CAP node.js App ?

EDIT:

So I did the principal propagation step but used the _srv address instead of the application address and all is working.

[gregorw]

Please add your edid as an answer.

[matteoprinetti · Accepted solution]

So turned out the problem I needed to address the _srv part of the application and not the application itself:

appname_srv_logon started web:1/1 appname.cfapps.eu20.hana.ondemand.com

appname_srv_logon-srv started web:1/1 appname.cfapps.eu20.hana.ondemand.com <==== pick this one

So boling down all the steps:

First have the Foundry system trust the NEO account

• export the SAML config from your NEO subaccount (under trust)
• import this file in the Foundry Subaccount

Then on Neo make a Destination using the Environment Variable from the appname_srv app on Foundry (see link above)

Both accounts must trust the same identity provider (in our case is the company AD Directory).

In order to "see" the foundry Destination on Neo Webide, set the properties WebIDEEnabled true and WebIDEUsage odata_gen.

Some notes of interest:

• Testing the connection from the Destination tab result in a 401 - metadata could not be read - this is OK you need to test for example creating an app in webide from a template and picking the Foundry Destination - you should see the entities etc.
• The approuter of your cap app on Foundry needs this line in the xs-app.json file:
  
  "identityProvider": "thestringofyouridpprovider"
  
  in case you have multiped idps that accept logon (in my case we have Standard idp and Corporate AD)