Mendix app on SAP Cloud - Cloud Foundry OData service error

Hi Mendix-community The set-up of the application is as follows: we want not-known-SAP/SCP end-users to access our Mendix application that’s going to need to consume an OData service of an OnPremise system. The documentation is rather contradictionary: use basic authentication, use principal propagation, us the GetDestination-method, use the GetCloudConnectorInfo-method, etc. There’s one constant in our quest, and that’s the HTTP 560 error, checking the logs: the hostname shouldn’t be known. Yet, when we deploy another application on CF (non-Mendix), we can perfectly access the OData service and fetch the data (with that same hostname). So I suppose that the Mendix application should as well be able to access the data, running in CF. Or do we need the proxy-object instead (returning object from the GetCloudConnectorInfo-method)? Anyone encountered this issue? Or know what the best workingway is regarding this issue? Thanks in advance!
3 answers

Edit: Make sure to open the images in a new tab, or download them. The microflows get cut off

So far, we have been forced to build our SAP OData requests manually, since the SAP OData Connector module does not support OData v4. We only use the module to get the Cloud Connector info. This is our process:


First, we get the CC info. Then we use that to check if you are running locally or not. We send one rest request, using basic authentication, to get a session cookie and token. Then we send another request, with the cookie and token, to get the actual data from the OData service. Here is what the process looks like:


The main Microflow:


Exclusive split (CC exists?):

SUB_authorize Call Rest:

For HTTP authentication use SAP User and Password

Find Token + Cookie (in main Microflow):

Main Microflow Call Rest:


Do you have a Cloud Connector installed, opening a tunnel for the OData service in the cloud? Without that, you will not be able to access an on-premise OData service.


To whom it may concern:

The solution to this problem was to accelerate to the next phase of the application development and start earlier with the integration of an ActiveDirectory.