Question

LTIMindtree Limited
US
Last activity: 17 Feb 2025 21:59 EST
facing Issues configuring OAuth with React starter Pack strict-origin-when-cross-origin with pega 23
Hello,
Following the steps https://community.pega.com/marketplace/component/react-starter-pack?
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.
Facing following ERROR:
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
Followed steps mentioned in but still facing issue :
Issues configuring OAuth with React starter Pack strict-origin-when-cross-origin | Support Center
Please ensure the following configurations:
Hello,
Following the steps https://community.pega.com/marketplace/component/react-starter-pack?
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.
Facing following ERROR:
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
Followed steps mentioned in but still facing issue :
Issues configuring OAuth with React starter Pack strict-origin-when-cross-origin | Support Center
Please ensure the following configurations:
- Update the CORS filter parameter in your web.xml.
Updatedwith following:
<init-param>
<param-name>cors.allowed.headers</param-name>
<param-value>If-Match,access-control-expose-headers,Authorization,Content-Type,X-Requested-With,accept,Origin,Access-Control-Request-Method,Access-Control-Request-Headers,x-constellation-app</param-value>
</init-param>
- Verify OAuth2.0 client registration and service package settings.
Updated - API and Application services both updated to use OAuth2.0 authentication
- Check for network-related issues.
No issues found – since authorize API is working, but
https://localhost.pegailt.net/prweb/api/oauth2/v1/authorize
- Ensure browser settings are not blocking requests.
No blocking requests from browser.