Incorporating an Iframe into one of my templates for authentication has presented certain challenges.
Case in point: When a user finishes a training session, they must verify their identity by authenticating with a ping identity server that will redirect to a different URL based on the entered credentials.
The Ping Identity platform is situated on a separate domain from the application itself. While I am aware of cross-origin issues, I have implemented a workaround by utilizing a server located in front of our app with the same domain to interact with the Ping Identity server internally. However, despite these measures, I still encounter CORS errors on the console. What would be the optimal approach to address this authentication issue, taking both user experience and security into consideration?