3724292 - Using 3rd party Web Application Proxy solution or Microsoft Entra private network end users are unable to connect or encounter connection issues when opening Stories and Models that rely on SAP BW4HANA connection in SAP Analytics Cloud

• A Web Application Proxy like Microsoft Marketplace | cloud solutions, AI apps, and agents is being used to let external end users access a BW backend system.
• External users can access the back end BW system directly using specific URLs but encounter issues when accessing the same endpoint to open Stories & Models in SAP Analytics Cloud.
• The steps outlined in KBA 2748971 - Error: "Access to XMLHttpRequest at <URL> from origin <tenant> has been blocked by CORS policy...", when connecting SAP Analytics Cloud (SAC) to BW - SAP for Me and 3677982 - Live Direct Connection to fails due to the local network access (LNA) specification - SAP for Me have been implemented.
• In the Browser Console log the following exception can be seen:
  • app.html#/dataanalyzer:1 Access to XMLHttpRequest at 'https://<mybwinstance>/sap/bw/ina/GetServerInfo?sap-client=<clientnumber>&sap-language=en&sap-sessionviaurl=X' from origin 'https://mybwinstance>' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
  • app.chunk.1513.f4e5c264124b3bdfb050.js:5  GET https://<mybwinstance>/sap/bw/ina/GetServerInfo?sap-client=<clientnumber>&sap-language=en&sap-sessionviaurl=X net::ERR_FAILED
    <mybwinstance>/sap/public/bw/ina/storageaccess/request.html:1  Failed to load resource: the server responded with a status of 404 (Not found)
    
    
• In the  Web Application Proxy session log the following can be seen:
  

• SAP Analytics Cloud (Enterprise)
• SAP BW Direct Connection
• Web Application Proxy - WAP Server / Microsoft Entra private network or a similar Proxy solution

1. Login to the Web Application Proxy.
2. Login to SAC Tenant.
3. Navigate to Data Analyzer and select a specific model or navigate to a specific Story or Model relying on the afflicted BW connection.
4. Select system type BW and connection name B4D.
5. An exception occurs in the Browser Console log with messages "Failed to load resource: the server responded with a status of 404 (Not found)" & "has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource."
6. Attempt to access the backend BW system via SAC as an external user using the getServerInfo URL - https://<mybwinstance>/sap/bw/ina/getserverinfo?sap-client=<clientnumber>
7. Metadata json file can be retrieved. 

• The issue is related to Cross-Origin Resource Sharing (CORS) configuration. The backend system does not include the 'Access-Control-Allow-Origin' header in the response, resulting in blocked requests due to CORS policy.

The solution of this issue is currently under investigation. Please follow this KBA for updates.

• Refer to: 2544696 - We couldn't connect to your (source) system / Failed to connect to (source) system creating / using a live data connection in SAP Analytics Cloud *** Collective KBA ***
• Refer to: 2748971 - Error: "Cross-Origin Resource Sharing (CORS) policy error when connecting SAP Analytics Cloud (SAC) to BW"

cross-origin resource sharing, cors error, preflight missing allow origin header, sac live data connection, bw system, external user access, failed to load query, sac data analyzer, blocked by cors policy, access-control-allow-origin header , KBA , LOD-ANA-LDC-BW , SAC Live Data Connection BW , Problem