Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-81030

Embedded Confluence pages broken with Custom Domains

XMLWordPrintable

      Issue Summary

      When the Custom Domain feature is configured, Confluence pages embedded from other Confluence sites become inaccessible.

      Steps to Reproduce

      1. Insert a link to another Confluence page from a different Confluence site.
      2. Configure it to be displayed as an embedded page.
      3. You should verify that the embedded page is displayed correctly.
      4. Configure the Custom Domain feature.
      5. Navigate to the page referenced in Step 1.

      Expected Results

      It is anticipated that the page will display embedded Confluence pages as it previously did.

      Actual Results

      Embedded Confluence pages are not being displayed, and the following error message is presented:

      <YOUR_SITE>.atlassian.net refused to connect.

      Workaround

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

            [CONFCLOUD-81030] Embedded Confluence pages broken with Custom Domains

            𝓅 added a comment -

            Hi everyone,

            This is Pascha from the Smart Links team. Thank you for bringing this issue to our attention.

            With the introduction of custom domains, embeds to resources that require authorisation will only work on the same domain. This is happening due to browsers strengthening security for cross-domain requests (e.g. disabling third-party cookies), and, while there are some workarounds that we can do when both sites are *.atlassian.net, there's no secure way to do so for custom domains, or even between custom and non-custom domain.

            To set the right expectations, we are closing this bug as ‘Won’t Fix' as we do not have any plans to change the behaviour of this feature. If this behaviour has a significant impact on your work, please share examples with us to help us understand your use cases when using this feature.

            Thank you again for providing valuable feedback to our team! I will be marking it closed for now.

            Pascha Aksenkin.

            𝓅 added a comment - Hi everyone, This is Pascha from the Smart Links team. Thank you for bringing this issue to our attention. With the introduction of custom domains, embeds to resources that require authorisation will only work on the same domain. This is happening due to browsers strengthening security for cross-domain requests (e.g. disabling third-party cookies), and, while there are some workarounds that we can do when both sites are *.atlassian.net, there's no secure way to do so for custom domains, or even between custom and non-custom domain. To set the right expectations, we are closing this bug as ‘Won’t Fix' as we do not have any plans to change the behaviour of this feature. If this behaviour has a significant impact on your work, please share examples with us to help us understand your use cases when using this feature. Thank you again for providing valuable feedback to our team! I will be marking it closed for now. Pascha Aksenkin.

              Unassigned Unassigned
              fa85d9e95975 Deniz Berkyürek
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: