Connecting internal fisheye to JIRA in the DMZ

Question

Initially we had both Jira and Fisheye on internal servers where they could be linked. The integration enabled the "source" tab in Jira where files from the commit shows up.

We have now moved Jira to the DMZ and we cannot expose the internal Fisheye since it is connected to git. Is there a solution to establish a connection such that the above mentioned integration is possible?

Alternatively we are looking to put Fisheye in the DMZ without direct access to Git, does this open up for any additional solutions?

In both of these cases, is there a solution to set up a connection through file exchange or email?

Josh Steckler · Answer

If the firewall is configured such that the only open port is 443, and only target of the proxy is those two application servers, yes it's a risk but a manageable risk. In my setup anyway, having JIRA and especially fisheye directly accessible through the internet on the dmz felt like a greater risk.

Dan Nguyen · Answer

It could be a solution, but wouldn't it affect the security of the internal network if a port has to be opened on the firewall for the proxy?

Josh Steckler · Answer

Rather than putting JIRA or Fisheye itself on the DMZ, could you put a proxy server on the DMZ and allow that proxy server through the firewall to the internal?

That way, both application servers would remain internal and have access to each-other.