Application link

[Simone Zoli]

Hi,

this is the scenario:

Jira -> https://jira.domain.com
Bitbucket -> https://bitbucket.domain.com

SSL is managed through reverse-proxy that is configured to accept only external request, even if the request come from the internal network (the internal DNS is configured with the public IP). 

But, for security policy, any connection between servers  MUST be managed inside LAN, so I can't use Bitbucket base URL to configure the applink with Jira.

So I've configured in bitbucket.properties a second http connector to create the applink.

The problem is that when an external user tries to create a branch (or something else) in Bitbucket from Jira, Bitbucket is called through the address configured in the applink, therefore through a private ip address or hostname (http://hostname:port).

The result is that external users can't reach bitbucket UI through Jira.

My question is: is it possible to have the applink configured with a private address but to reach bitbucket by its pubblic address?

Simon

[Tzu Hau Chai]

Define an additional HTTP connector for JIRA, listening to a different port (do this for Bitbucket as well). This is necessary as the existing connector used by the reverse proxy has proxy related parameters configured (ie. proxyName, proxyPort in Tomcat).

Then, setup the application link in the following way:

JIRA:
Display URL: https://bitbucket.domain.com
Application URL: http://<internal ip>:<new connector port>

Bitbucket:
Display URL: https://jira.domain.com
Application URL: http://<internal ip>:<new connector port>