iFramed Support

Historically iFrame/xframe worked with a CAS Authentication along with a legacy home grown portal. While migrating to a Service Now instance and switching to Azure for authentication issues are experienced both requiring authenticating twice when it was working on Netreo release 2022.1 release 12 but is not working on releases 8, 20 and 43.

This is impacted on Chrome, Edge and Safari. FireFox does not work fully as it breaks the iFrame/xFrame out and relaunches the window outside of the framework. This exposes menus and reporting areas that we do not always want to have exposed.

iFrame / xFrame is fairly standard with other monitoring platforms such as Solarwinds
(https://support.solarwinds.com/SuccessCenter/s/article/NPM-11-5-and-later-prevents-an-iFrame-from-displaying-within-an-external-web-site-or-a-custom-web-page?language=en_US) and Datadog: (https://docs.datadoghq.com/dashboards/widgets/iframe/)

Prior to this engagement, we have not seen this behavior with a web application -- apps have loaded in SNOW portals without the need for additional configuration at the browser level. It is believed this behavior can and should be corrected within the Omnicenter web app, citing the following links as possible leads to resolving this issue:

https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-browser/docs/iframe-usage.md

https://github.com/AzureAD/azure-activedirectory-library-for-js/wiki/FAQs#q4-i-get-this-error-refused-to-display--in-a-frame-because-it-set-x-frame-options-to-deny

We would like to see support from Netreo for iFrame / xFrame which is not currently a supported feature.