SSL Application Link to Jira

Serge Dukic February 18, 2013

Hi

I've got a Stash server running over SSL, on port 8443: https://stash:8443/ It is using a self-signed certificate for the encryption.

I'm trying to create an application link between our Jira instance (non-SSL, HTTP) and the Stash instance. I have imported the self-signed cert into the keystore as described in the answer here. In addition, I've downloaded the SSLPoke application and confirmed that I am able to connect from the Jira server:

# java SSLPoke stash 8443
Successfully connected

I've also confirmed that the REST API (which I assume is being used for the application links) is running on port 8443 by checking that URLs such as these return valid data:

https://stash:8443/rest/api/1.0/profile/recent/repos

The error I get when I try to create an application link from Stash reads:

The Remote application is not able to connect to 'Stash'(Stash) by using the URL 'https://stash:8443'.

When I try to create the link from Jira, the errors displayed are:

The host is unknown. Verify that the URL is correct.
The specified URL does not appear to be an instance of the selected type.

Does anyone know what could be the problem here? Am I wrong in assuming that the application links use the REST API? If so, what ports need to be accessible to enable SSL application links between Jira and Stash?

1 answer

1 accepted

2 votes
Answer accepted
pkirkeby
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 19, 2013

Were there any errors in the logs that seem relevant?

I would start by confirming if the certificate is stored in the correct Java keystore. Its possible JIRA is unable to connect to Stash over SSL because of the certificate not being available. You can use this plugin for a simple way to connecting/importing a SSL cert:

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

Serge Dukic February 19, 2013

It was in fact the wrong JRE that had the certificate added. Jira was using a different JRE than the standard system one.

Felix Lebel February 11, 2015

I just came to the same conclusion! It can be found here: /opt/atlassian/jira/jre/lib/security/cacerts

Suggest an answer

Log in or Sign up to answer