Issues configuring OAuth with React starter Pack strict-origin-when-cross-origin

General
, , , ,
1

Hello,

Following the steps React Starter Pack | Pega?

Using LinuxLite-Pega231.ova and have configured the NVM and followed the instructions to setup Cableconnect App.

Using OAuth2.0 authentication, I am unable to log in with strict-origin-when-cross-origin / 403 error.

API and Application services both updated to use OAuth2.0 authentication.

Could you please help identifying the missing configuration.

Required screenshots attached.

Thanks

endpoints.jpg
endpoints.jpg1235×799 115 KB

error.JPG
error.JPG1249×975 109 KB

OAuth 2.0 Client Registration.JPG
OAuth 2.0 Client Registration.JPG1110×693 65.9 KB

2

@chamilaf

Please ensure the following configurations:

  1. Update the CORS filter parameter in your web.xml.
  2. Verify OAuth2.0 client registration and service package settings.
  3. Check for network-related issues.
  4. Ensure browser settings are not blocking requests.

If the issue persists, further details or screenshots may be needed.

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

Setting up an OAuth 2.0 client registration

Configuring Pega Mobile Client to authenticate against Okta

React Starter pack

If you need further help i suggest you log a support ticket via the MSP, detailing which area of product is not behaving as documented.

cc @Sam Alexander do you know who is the Owner of the Marketplace offering React Starter Kit?

3

@MarijeSchillern ,@chamilaf

I have followed same step using LinuxLite-Pega231.ova and have configured the NVM and followed the instructions to setup Cableconnect App.

Start Button and then clicked on login button by using username and password, I am getting CORS failing error at token

Updated - Allowed hearder orging with x-constellation-app

Error :auth:1 Access to fetch at ‘https://PegabaseURL/prweb/PRRestService/oauth2/v1/token’ from origin ‘http://localhost:3000’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. If an opaque response serves your needs, set the request’s mode to ‘no-cors’ to fetch the resource with CORS disabled

any suggestion?

Thanks

Srinivas Bomma

4

@Bomma Srinivas I notice you posted a similar reply on another old post here.

Please can you post a New Question instead?