Consuming SAP ODATA V2 in public cloud via Destination

Hi all, I was tasked with writing a Mendix App, which is supposed to be running on the BTP in an SPA Public Cloud Solution. I started with Basic Authentication and running it locally it worked perfectly fine. Then I deployed it on the BTP and it didn't work anymore, but that wasn't unexpected, so I started troubleshooting. I was told, I need to use a Destination, so I had someone set up a Destination in the BTP using the credentials of the User I used up to then. I read up and found that I have to use XSUAA when using a Destination while running on BTP, so I changed the Login to XSUAA, added a GetDestination, removed the RequestParams from the GetList and added the Destination instead. Also I switched the Constant XSUAAEnabled to true and removed the Service Root from the Request URL, as stated in the documentation for OData Connector for SAP Solutions. Now I can log in with XSUAA in a new private window, but not when already logged in, but that's a comparably minor issue. Whenever I try to get data I only get an 403 and the log shows the following: 2023-10-24T10:46:05.306Z [APP/PROC/WEB] OUT INFO - Destination Service: Request User Access token 2023-10-24T10:46:05.911Z [APP/PROC/WEB] OUT INFO - Destination Service: The Destination s4_api_access fetched with authentication type BasicAuthentication and proxy type Internet. 2023-10-24T10:46:05.911Z [APP/PROC/WEB] OUT INFO - Destination Service: GetDestination action successfully completed 2023-10-24T10:46:05.945Z [APP/PROC/WEB] OUT INFO - ODataConnector: GetList:: Destination found, retriving list. 2023-10-24T10:46:05.982Z [APP/PROC/WEB] OUT INFO - ODataConnector: dcfee4d7-eb71-48f5-bc9a-0a068c9ddc21|Request URI: /YY1_SupplierPostTime_API?$filter=Supplier%20eq%20%2710000241%27&?$orderby=PurchaseOrder,PurchaseOrderItem,PersonFullName,Project,TimeSheetDate 2023-10-24T10:46:06.047Z [APP/PROC/WEB] OUT INFO - ODataConnector: dcfee4d7-eb71-48f5-bc9a-0a068c9ddc21|Response Received Status Code: HTTP/1.0 403 Forbidden Does anyone have an idea why I still can't access the service?
0 answers