Connecting Confluence Cloud to Jira Data Center via Atlassian Tunnel Using Forge – Seeking Guidance

[Juan Ramón Alonso García]

We currently have a Confluence Cloud instance that needs to retrieve information from a Jira Data Center (DC) environment located inside our internal network, behind a firewall.

We have successfully tested the Atlassian tunnel using the Legacy Jira Macro in Confluence Cloud — we can access Jira DC work items from Confluence Cloud without issues. However, the Assets Macro only works with Jira Cloud, so we decided to develop a proof of concept (PoC) using a Forge Macro that connects to our Jira DC via an Application Link configured to use the Atlassian tunnel.

According to the documentation, calling a REST API endpoint through the Atlassian tunnel should be straightforward, as the tunnel is expected to forward the request to the internal endpoint. However, so far we haven’t been able to reach our Jira DC instance.

When attempting to reach Jira DC from the resolver, we get an ERR_ACCESS_DENIED response from an intermediate SQUID server (whose origin we’re not sure about). When trying to reach it from the frontend using requestJira, we encounter a CSP violation.

I realize this isn’t enough information to fully troubleshoot the issue, but my question to the community is:

Has anyone successfully used the Atlassian tunnel to connect to a backend service behind a firewall?
Does this setup work with Forge, or is the tunnel effectively limited to Atlassian’s internal integrations?

I’d really appreciate hearing about your experiences or any advice you might have on this.

Cheers all!