Is Mashup used in Production for any client with Pega 8.6? Any known issues?
Hi,
I need official information coming from Pega on the following -
1. Is Mashup used in Production for any client with Pega 8.6? Any known issues?
2. Is mashup advised to be used for clients in Production?
3. What are the authentication options present with Mashup apart from basic authentication and how to implement those?
Pegasystems Inc.
GB
@arkaB871 for your version of Pega see Best practices for using mashups
Details about authentication options with Pega 8.8 Mashup are documented in a sub-section of Pega web mashups for embedding traditional UI in external web pages.
I will leave other forum users to comment on their experience using Mashup.
Updated: 6 Jul 2023 6:20 EDT
OFG Group Ltd
IN
Hi Marjie,
Hope you're doing well! Thanks for the response.
A couple of follow up questions -
1. Is it true that Mashup is not recommended to be used in production due to the known issues?
2. Can we have some official metrics from Pega where Pega can share the count of clients for which Mash up generated code is successfully being used in Non-Pega web pages to embed Pega screens (restricting to Pega version 8.6).
3. Can we have the list of known issues reported on Mash up (till Pega version 8.6) when used to embed the Pega screens in Non Pega Web pages?
4. Can we use oAuth2.0 as authentication mechanism with Mash up?
Thanks,
Arka Bhattacharya
Updated: 6 Jul 2023 7:12 EDT
Pegasystems Inc.
GB
Hi . @arkaB871 I can find no externally-facing metrics available. You may want to speak to your Pega AE if you need this type of information.
I'm not aware of any production level problems. Perhaps you can clarify where your concern come from?
Troubleshooting browser-specific issues with mashups
Troubleshooting issues with loading mashups
Mashup issues with cross-domain (X-Frame) communication
Troubleshooting Pega mashup issues caused by browsers blocking third-party cookies
Cannot load the same mashup again based on conditions
Pega Web Mashup security concerns
Hi . @arkaB871 I can find no externally-facing metrics available. You may want to speak to your Pega AE if you need this type of information.
I'm not aware of any production level problems. Perhaps you can clarify where your concern come from?
Troubleshooting browser-specific issues with mashups
Troubleshooting issues with loading mashups
Mashup issues with cross-domain (X-Frame) communication
Troubleshooting Pega mashup issues caused by browsers blocking third-party cookies
Cannot load the same mashup again based on conditions
Pega Web Mashup security concerns
Known issues and Resolved issues can all be found on the docs-previous and PSC Resolved Issues search pages:
Nagarro
IN
Anonymous authentication can also be used while using Mashups. Create an anonymous auth service and then replace the URL in the mashup script. Also, I have never used OAuth with mashup, but it can be implemented (POC needs to be done).
If you use mashups then session management needs to be handled. IF you use session timeout our of the box then on log off, Pega Log off screen will be displayed which is not for end user facing applications. So, you have to customize either Pega log off screen or Log Off activity needs to be customized.
Always use Pega mashup code instead of iFrame code for mashups.
Also, UI/UX needs to be in sync with the parent website (Typography,fonts,etc). Also, if you redesign log off screen typography and fonts cannot be achieved same as parent website because once logged off you cannot access the CSS and other artifacts which are present in Pega. Either you need to host in a CDN server or study the cache manifest file. How Pega generates it ?
If pega content is too big then an additional scroll bar will appear on the UI. IT will not look good as there might be two scroll bars on the UI (one from parent website and another one coming from Pega screen).
Cross site security needs to be handled.
Content security policy should be designed well.
Anonymous authentication can also be used while using Mashups. Create an anonymous auth service and then replace the URL in the mashup script. Also, I have never used OAuth with mashup, but it can be implemented (POC needs to be done).
If you use mashups then session management needs to be handled. IF you use session timeout our of the box then on log off, Pega Log off screen will be displayed which is not for end user facing applications. So, you have to customize either Pega log off screen or Log Off activity needs to be customized.
Always use Pega mashup code instead of iFrame code for mashups.
Also, UI/UX needs to be in sync with the parent website (Typography,fonts,etc). Also, if you redesign log off screen typography and fonts cannot be achieved same as parent website because once logged off you cannot access the CSS and other artifacts which are present in Pega. Either you need to host in a CDN server or study the cache manifest file. How Pega generates it ?
If pega content is too big then an additional scroll bar will appear on the UI. IT will not look good as there might be two scroll bars on the UI (one from parent website and another one coming from Pega screen).
Cross site security needs to be handled.
Content security policy should be designed well.
Also, if you use mashup then anyone can use inspect element and copy the pega applciation URL and access the application. So, you need to implement that security as well.
There are lot of aspects while you implement mashup. Please check the above points as well while you design your use case.
Do let me know if you have more questions :)