Question
Blue Rose Technologies
BE
Last activity: 1 Nov 2024 8:35 EDT
CORS error when trying to run a pega webembed from a custom HTML file from browser
We have created an application on constellation in pega labs.
created a web embed to create a case.
created a html page with this web embed code and then placed it in our local machine tomcat.(to launch it as http://localhost:8080/docs/WebEmbedTest_XYZ.html)
when the html is run from the browser then it asks for credentials and successfully showing the pega case.
which means web embed is working fine with basic auth.
https://XYZ.pegalabs.io/prweb/
Problem scenario :
1. we have created a authentication service /prweb/PRWebLDAP1
2.generated the web embed code again and updated the pega URL with this URL created in step1.
https://XYZ.pegalabs.io/prweb/PRWebLDAP1/
3. Now when we try to load the HTML page in the browser then it shows
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://XYZ.pegalabs.io/prweb/PRWebLDAP1/PRRestService/c11nsvc/v1/config. (Reason: CORS request did not succeed)
Accepted Solution
Updated: 1 Nov 2024 8:35 EDT
Pegasystems Inc.
US
@Pavan Kumar Koduri
The authorization code grant flow is failing. Look at the response within the authDone.html for more details (likely there is output in the console as well). Something is misconfigured. &error_description and &error query args to that redirect uri will give you the details of what is going wrong. What is the value for authentication_service argument for the authorize endpoint transaction within that network trace? Is that the identical value for the "authentication service alias" you have in your authentication service rule?
Pegasystems Inc.
US
@Pavan Kumar Koduri
With Constellation Web Embed, the pegaServerUrl should be just up to prweb. The way to get a custom authentication service to be utilized by Web Embed is to use the authService attribute and populate that with the "Authentication service alias" associated with your custom authentication service. So it would then be something like authService="WebLDAP1", and the pegaServerUrl="https://XYZ.pegalabs.io/prweb/" Can you please give that a try?
Blue Rose Technologies
BE
Thanks for the answer.
I have (already) tried the above solution .
The screen shows forever rotating busy icon.
And the network trace shows like this.
Any idea what else could be the issue?
Accepted Solution
Updated: 1 Nov 2024 8:35 EDT
Pegasystems Inc.
US
@Pavan Kumar Koduri
The authorization code grant flow is failing. Look at the response within the authDone.html for more details (likely there is output in the console as well). Something is misconfigured. &error_description and &error query args to that redirect uri will give you the details of what is going wrong. What is the value for authentication_service argument for the authorize endpoint transaction within that network trace? Is that the identical value for the "authentication service alias" you have in your authentication service rule?