Issue Summary

When a Confluence article containing macros (/iframe) is published to the CSM Support Site/customer portal, the embedded content fails to render for customer users. The macro embeds a Confluence page URL via iframe, which triggers an authentication request to id.atlassian.com. The customer portal environment blocks this cross-origin iframe authentication request, causing browser-specific rendering failures. 

Steps to Reproduce

1. In Confluence, open an article in Edit mode

1. Type /iframe (Just example could happen to other macros too) and insert the Iframe macro, linking to another Confluence page URL

1. Publish the article so it is visible on the CSM customer portal

1. Log out of the agent view and access the portal as a customer user

1. Navigate to the published article and observe the rendering behaviour across browsers

Expected Results

The macro renders the embedded Confluence page content correctly for the customer within the portal.

Actual Results

The Iframe macro fails to render for the customer, with browser-specific symptoms:

• Chrome: Broken image displayed with the error "id.atlassian.com refused to connect"

• Safari: Blank white page with no content displayed

• Firefox: Error stating the embedded id.atlassian.com content cannot be displayed due to security/embedding restrictions; however, the page loads successfully when opened directly in a new tab

Note: The agent view of the same article is unaffected — the issue occurs only in the customer-facing portal view.

Workaround

As a temporary measure, avoid using the macro in CSM portal articles. Where possible, replace iframe-embedded links with standard hyperlinks or Confluence Smart Links in Card or Inline display mode (not Embed), as these do not trigger cross-origin iframe authentication requests.