Question
Cognizant Technologies
IN
Last activity: 4 Dec 2024 4:09 EST
Not able to implement WebEmbed exercise
Not able to implement WebEmbed exercise in Implementing web embed interfaces om LSA -> Pega Design exercise challenge.
Followed the instructions in the challenge.
Updated the generated client ID in the web embed code.
Clicking on case1.html the system does not render the new created case.
Please advise.
Accepted Solution
Updated: 4 Dec 2024 4:07 EST
Cognizant
IN
Hi Ravi
Please invoke the sample web embed using https://localhost.pegailt.net/PASample/ since the origin null indicates the local file system and you need to access it from the web where it is deployed.
Eclatprime Digital Private Limited
IN
- In Chromium-based browsers, ensure that in the Cross-site Request Forgery system setting, in the Cookie settings section, the Enable samesite cookie attribute is checked, and the Sometime options drop-down list is set to None.
For more information, see Mozilla developer guidance.
- Verify if the Content-Security-Policy header returned by one of the redirect responses is not stopping the authorization from completing in the hidden iframe. Values to consider are:
script-src,frame-src,sandbox,frame-ancestors, andnavigate-to. - If the redirect sequence to the identity provider is very slow, then increasing the timeout interval might prevent the pop-up window from appearing.
- If the authentication fails in the hidden iframe, ensure that the server that authorizes the endpoint is not configured to return the X-Frame-Options header with a response of
SAMEORIGINorDENY. If you fix this configuration, the authentication redirects in the hidden iframe should succeed. Consequently, the pop-up window does not appear.
Pegasystems Inc.
IN
@Ravi Balasubramaniam - Can you share the screen shot of webembed screen run time .If any errors are seen on browser developer tools console tab share the screen shot.
Thank you.
Updated: 2 Jun 2024 13:45 EDT
Cognizant
IN
Facing similar issue with the web embed exercise in CLSA Infinity ’23 course.
When I click on the external html page area containing the web embed, it just clocks. I can see error on browser developer tool console.
Here is the webembed code. I used custom bearer grant type.
<script src='https://prod-cdn.constellation.pega.io/8.23.0-110/react/prod/pega-embed.js' ></script>
<pega-embed id='theEmbed' action='createCase' caseTypeID='MDC-Reg-Work-Partner' casePage='full' appAlias='registration' pegaServerUrl='https://localhost.pegailt.net:443/prweb' staticContentUrl='https://prod-cdn.constellation.pega.io/8.23.0-110/react/prod/' grantType='customBearer' clientId='12439742307580435200' style='width:100%'>
</pega-embed>
Attached browser error screenshot
In the Endpoint-CORS policy mapping I was able to see
Endpoint * mapped to AllowAllOrigins CORS policy
Not sure how to fix it for quite some time. Please help.
Pegasystems Inc.
IN
@SohiniD775 - Can you verify the DSS " api.v1.CORS.allowedheaders" any changes are done other than -authorization, content-type
Thank you.
Cognizant
IN
I verified that the DSS api.v1.CORS.allowedheaders has the value 'authorization, content-type' only.
Updated: 29 Nov 2024 6:47 EST
Cognizant Technologies
IN
@Priyanka Boga here is the screen shot of the console, appreciate ur help.
Accepted Solution
Updated: 4 Dec 2024 4:07 EST
Cognizant
IN
Hi Ravi
Please invoke the sample web embed using https://localhost.pegailt.net/PASample/ since the origin null indicates the local file system and you need to access it from the web where it is deployed.
Cognizant Technologies
IN
@SohiniD775 thanks a lot Sohini. it worked like clock work with a bit of delay though. Appreciate ur help.
Virtusa
US
seems like you might have missed to update OAuth2 service package pointing to right service access group DeliveryService:Users