PEGA and Angular connectivity. External API locking

General
, , ,
1

Good morning

We are finding some connectivity problems between PEGA and Angular

If we run our P1 app we get an error, but CORS configuration is locking the response provided by PEGA API. We get a 200 Ok message, which means we can connect with the external server (PEGA API) but the response es locked by CORS.

Our API 1.png
Our API 1.png1907×116 91.2 KB

Our API 2.png
Our API 2.png1636×653 165 KB

However, executing the same test by using Starter-Pack app, the response provided by PEGA API is not locked and we can visualize data provided by API with no problems.

Starter Pack 1.jpg
Starter Pack 1.jpg838×659 83.3 KB

Starter Pack 2.jpg
Starter Pack 2.jpg1373×653 207 KB

The only difference we can appreciate by comparing both apps is that Starter-Pack just send a request to PEGA API, but there is no back component. In the other hand, our P1 app has got a back component to send different requests (internal ones to our P3 API and external ones to PEGA API too). So we think there are some mistakes in our configuration to avoid external API locking

Please could you throw some light on this?

Thanks in advance

Kind regards

2

@RafaelM17133850

To resolve the CORS issue, ensure your P1 app’s back component includes the appropriate CORS headers in the response. Configure the CORS settings in your web.xml or server configuration to allow the necessary headers and methods. Additionally, ensure the server hosting your P1 app handles preflight requests correctly and includes the Access-Control-Allow-Origin header in the response.

:warning: This is a GenAI-powered tool. All generated answers require validation against the provided references.

If you believe product is not behaving as documented please log a support issue via the MSP and provide the INC id here.