Constellation SDK on Community edition 25.1.2

[HarmD (Harm Doedens)]

Background: We are using Constellation SDK in Portal mode for our client facing custom user portal. We are running Pega 24.1. In preparation for the upgrade to Pega 25 I am trying to test our portal setup against a Pega 25 instance to see what React code needs to be updated (we have a lot of custom code to suit our multi-client portal set-up.

To get started I am trying to get the Basic Constellation SDK (MediaCo) working with Pega 25. For that I fired up a Community Edition. I followed the steps in Pegasystems Documentation .

When I start the local server with npm run start-dev and navigate locally to http://localhost:3502 a pop-up window appears for authentication. I fill in the username and password, the pop-up window disappears and then I get this error:

Cross-origin script load denied by Cross-Origin Resource Sharing policy.

I have tried several things:

• Update DSS allowedheaders with Access-Control-Allow-Origin
• Updated Endpoint-CORS policy mapping.
• Added Access-Control-Allowed-Origin to APIHeadersAllowed CORS rule.

The error persists and I have no idea where to look next. Does anybody has the same issue or a possible solution?

[JayachandraSiddipeta]

Hello @HarmD

In the OAuth Client registration instance, add your localhost entries as shown below. This should avoid the CORS error and your SDK config and bootstrap should be loaded from your local instance SDK packages.

Hope this helps.

Regards

JC

[MarcCheong]

@HarmD have you joined the User Experience Expert Circle?

We have some videos on there that may also be useful:

• DX component building within sdk
• Extending Constellation UI: DX Component Full Lifecycle | Pega

We used them in Extending Constellation: A Deep Dive into Constellation DX Components | Pega , if any of those resources help

[NielsHeinis]

Answering on behalf of Harm since he’s having trouble replying in the forum.
This is the configuration of his OAuth Client Registration. He is using the default port number: 3502, but that should not be any problem.

[JayachandraSiddipeta]

Also you CORS APIHeaderAllowed should look like below,

Regards

JC