Configuring the iFrame macro to render the same instance within a third-party app does not work

Issue Summary

By default, Confluence cannot be rendered via an iFrame in external sites due to the 'sameorigin' policy in the X-FRAME options for Atlassian Cloud (CONFCLOUD-66693).

When using the iFrame macro to point it to Jira/Jira Service Management in the same instance, it will allow the content to be displayed. However, if the macro is added within a third-party app macro, it will fail:

Refused to display '<URL>' in a frame because it set 'X-Frame-Options' to 'sameorigin'.

Steps to Reproduce

1. Have Confluence and Jira configured in the same instance (I.E. https://INSTANCE.atlassian.net for Jira and https://INSTANCE.atlassian.net/wiki for Confluence).
2. Create a Confluence page and insert the iFrame macro, configuring it to point to Jira.
3. Add this macro within a third-party macro, like the Tabs from Navitabs. Notice that the macro properly displays the Jira content within the iFrame while being edited.
4. Publish the page.

Expected Results

As in the "edit" mode, the iFrame should render the Jira content from the same instance.

Actual Results

The iFrame within the third-party macro displays the following message:

INSTANCE.atlassian.net refused to connect.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.