Support Article
Mashup does not load with dynamic domains
SA-81344
Summary
Operators in a third-party system experience Cross Origin Resource Sharing (CORS) warnings in the console when accessing the Pega application on the Chrome browser.
Error Messages
Not Applicable
Steps to Reproduce
Not Applicable
Root Cause
The client used a Mashup that was used in dynamic domains. The Mashup Security section in the application record on the Security and Integration tab did not allow for wild cards, https://*.myco.ca.
The client did not want to define all the sub domains in this record where the Mashup would be displayed, because the list would get large.
Resolution
The top-level application will know the sub-domain in which the page is displayed.
- Add a parameter to the Mashup to specify the domain.
- At runtime as part of post authentication, modify the Application.pyMashupHostDomainList which is a Data-PWMashup page group.
data-pega-action-param-parameters="{UserIdentifier:'<user>',isWebMashup:'true', acceptDomain:’east’}"
The application record specifies https://*.myco.ca.
- Take the acceptDomain parameter in custom configuration, such as in the ApplicationProfileSetup activity or before the page displays and dynamically modify the Application.pyMashupHostDomainList(1).
- Replace the '*' with the value of acceptDomain which results in: https://east.myco.ca.
Published August 15, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.