I'm working on a project where we want to include an authenticated microfront end within our Pega application. The idea is to have a separate team work on a ReactJS component that can be integrated into the Pega platform. This component will be hosted on a separate CloudFront or Nginx server, allowing the component team to make changes and publish updates independently, with minimal impact on the Pega application. Additionally, the ReactJS component uses authentication, which we must consider during the integration process.
To achieve this, I'm exploring different designs and approaches that would allow for seamless integration of the ReactJS component into Pega. I hope to engage with the community to gather your valuable insights, experiences, and suggestions on the best way to achieve this.
Here are some questions I have:
Has anyone previously attempted to integrate an authenticated microfront end like this in a Pega application? If so, what were your experiences, and what lessons did you learn?
What are some best practices for including an authenticated ReactJS component in Pega, particularly in maintaining performance, compatibility with Pega's UI and workflows, and securely handling authentication?
How can we best manage the authentication process between the Pega application and the ReactJS component to ensure a secure and user-friendly experience?
I'm looking forward to hearing your thoughts and exsecperiences on this topic.
***Edited by Moderator Marije to add Capability tags***
@Imranullah-db Did you find an apt approach. It would be really beneficial if you can share your experience and answers to your questions here, again assuming you would have already started on it. We too have a similar requirement.