nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Application linking with SSL proxy in front of JIRA and Confluence server

Nariman Riahi1

We have a setup where both Jira and Confluence are installed on the same machine (ports 8080 and 8090 respectively). There is a proxy in front of the server that does SSL termination for both applications. The application context for Jira is /jira and for Confluence is /confluence.

I can not link applications. In App link screen I put the URL to the other app and when I click NEXT, nothing happens on the screen.

Browser console says the following communication fails:

https://jira.corp.company.com/jira/rest/applinks/1.0/applicationlinkForm/manifest.json?url=https://jira.corp.company.com/fecru/&_=1340725908493

The Jira remote API is enabled.

Atlassian says "The configuration of your proxy is outside of the scope of support" (thank you Atlassian). So if anyone can help me solve this problem I would really appreciate it.

Accepted answers

Farzad Panahi2

I fixed my problem by adding SSL to cacert files of JREs for both Jira and Confluence. Read more here.

All comments

Nariman Riahi1

I was able to successfully configure the application link by installing and configuring apache with mod_proxy on our server along with setting my host file on my client workstation to point directly to the server.

Once the application links were set I was able to remove the host entry and everything operated as expected.

Yannick Morin-R2

Can you give more details, i think we are a lot of people having the same problem !

Farzad Panahi2

I fixed my problem by adding SSL to cacert files of JREs for both Jira and Confluence. Read more here.

Dave C

It sounds a bit strange that you'd need to workaround it in that manner and suggests there may have been some issues with the configuration. If you're using HTTPS offloaded at Apache, you'll need to ensure that the Tomcat connectors have been configured as proxy connectors rather than standard connectors. Also, if you're offloading HTTPS and using a self-signed certificate or self-signed CA, each application will need to have either the cert or CA loaded into the trust store. In case you missed these:

https://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Apache+using+SSL

https://confluence.atlassian.com/display/DOC/Using+Apache+with+mod_proxy

The important things to remember are setting the proxyName, proxyPort and scheme parameters on the HTTP connector and also disabling http compression in Confluence and GZip compression in JIRA.

If you need to import the certificates from each other's server, you could use the following plugins:

https://marketplace.atlassian.com/plugins/com.atlassian.confluence.plugins.ssl

https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugin.jirasslplugin

I'm happy to take a look through your configuration if you'd like - if so please provide details of:

The httpd.conf file.
Tomcat and JIRA server.xml

Justin Donnarum

Could you post that in a place everyone can get to? It would be much appreciated.

Dave C

Sounds like Farzad is referring to adding the public certificates of the applications to the JIRA and Confluence Java trust stores, cacerts. We have info on how to do this in https://confluence.atlassian.com/display/JIRA/Connecting+to+SSL+services.

Farzad Panahi2

That page used to be a public one. I don't have access either now.

But as David mentioned I think I just added the public certificate of each app to the other app's jre trust store.

Jonas Andersson

I am a bit lost on the subject too, but managed to get it to work to 90%.

We run JIRA and confluence on the same machine, both using http only in tomcat. We deployed a apache mod proxy in front of it that does the SSL termination for both applications, using virtualhost that forwards the respective fqdn to it's respective ports (i.e jira.example.tld points to port 8080, confluence.example.tld points to 8090.

When setting up application trust i was forced to bypass the proxy, so instead of using https://jira.example.tld we use http://jira.example.tld:8080. For Activity streams, linking to JIRA tickets on confluence this config works fine, but some things (like linking a JIRA to a confluence document) it claims that the application-url is wrong.

Question: Should i use FQDN or short names in the mod proxy, application-links, baseurl, and so forth?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira

application-link