confluence link to JIRA for project management
Asked by Pavel Ihring:

Hello!

We use separate (timely and by license) installations of JIRA (v 6.1.6) and Confluence (v 6.6.1)

Both installations use https.

We tried to connect Confluence to JIRA for project management so that we can/modify see JIRA issues in Confluence.

We followed the Confluence documentation to do this (e.g. <https://confluence.atlassian.com/doc/connecting-to-crowd-or-jira-for-user-management-229838465.html>)

The first step on JIRA side was ok:

![image.png](/t5/image/serverpage/image-id/14486iB3E3D1F7D17EC56B/image-size/large?v=v2&px=999 "image.png")

Step 2 on confluence side was not ok.

When entering server URL (for JIRA) the same as JIRA Base URL we get the following error:

![image.png](/t5/image/serverpage/image-id/14487i26A4B02E73F368F6/image-size/large?v=v2&px=999 "image.png")

Don't know if this has something to do with using SSL for both confluence and JIRA ... ?

Or perhaps it is related to the fact that both jira and confluence reside on the same IP address, just using different ports? How can I specify the ports when linking the applications?

Can you please advise a solution?

Many thanks in advance.

gajdosik@proximard.sk


Answers:
author: Thomas Deiler
body: Dear [@Pavel Ihring](/t5/user/viewprofilepage/user-id/1185994),

it seems that the SSL certificate is not known and cannot be trusted. You can either

1. add the cert to the current [keystore of JRE (first long answer)](https://community.atlassian.com/t5/Jira-questions/How-to-add-CA-cert-to-Jira-s-trust-store/qaq-p/720158 "How to add CA cert to Jira's trust store?")
2. purchase a valid CA signed certificate (eg. LetsEncrypt)

So long

Thomas

comments: author: Pavel Ihring
body: Hello Thomas!

Thank you for your advice. We did as suggested but the message is the same still.

What I did:

1) I generated a self-signed ssl certificate with keytool as recommended in <https://confluence.atlassian.com/doc/running-confluence-over-ssl-or-https-161203.html>

and substituting google.com:443 by our JIRA base URL (xx.xx.xx:443)

Should I use 8443 instead?

2) I imported the certificate into trusted java keystore as recommended by your post

Can you please specify what should be the value of the -alias parameter when inserting the certificate into the keystore?

Many thanks in advance!

gajdosik@proximard.sk

pauli@proximard.sk


author: Thomas Deiler
body: Dear [@Pavel Ihring](/t5/user/viewprofilepage/user-id/1185994),

the alias should be same as how you connect to Jira/Confluence:
> <https://server.com> ----\> alias = server.com:443
>
> <https://server.com:8443> -----\> alias = server.com:8443

So long

Thomas


author: Thomas Deiler
body: Dear [@Pavel Ihring](/t5/user/viewprofilepage/user-id/1185994),

has your cert now been accepted?

So long

Thomas


author: Pavel Ihring
body: Hello Thomas!

Thanks for your reply.

My problem persists, here is what I have done in between:

**1) purchased CA SSL certificate**

Both JIRA and Confluence installations are on the same server and they use this CA certificate. When logging into both systems, we have the green connection status "Secure".

**2) deleted all attempts on linking the systems from the past (i.e. all application links, user directories, ...), so starting the linking from scratch**

**3) tried to create application link from Confluence**

according to the description at

<https://confluence.atlassian.com/doc/linking-to-another-application-360677690.html>

steps 1, 2, with **I am an administrator on both instances** checkbox selected

indeed, the same username/password are used on both systems with admin permissions

++**Result:**++

- I'm said to be redirected to JIRA, prompted for login credentials

- the URL is switched to our JIRA Administration -\> Add-ons -\> Configure Application Links screen

- a popup appears saying:

Unable to create reciprocal link. {#toc-hId-1792436896}
-------------------------------------------------------

It has not been possible to retrieve the required information from https://\<my.jira.server\>:8444. Therefore the link cannot be created.

Thait is, JIRA attempted to retrieve something from confluence (confluence is at port 8444)

Please advise, I'm out of options here.

Many thanks

gajdosik@proximard.sk

pauli@proximard.sk


author: Thomas Deiler
body: Did you have a look in both server log files? What are the errors?


author: Pavel Ihring
body: Hello,

the JIRA side log:

2018-03-20 17:36:15,325 http-bio-443-exec-1 WARN adminconf 1056x15913x1 ecax3t 212.5.222.82 /plugins/servlet/applinks/listApplicationLinks \[atlassian.applinks.ui.BatchedJSONi18NBuilderFactory\] Duplicate i18n entry for key 'applinks.auth.provider.com.atlassian.applinks.api.auth.types.OAuthAuthenticationProvider'  
2018-03-20 17:36:15,325 http-bio-443-exec-1 WARN adminconf 1056x15913x1 ecax3t 212.5.222.82 /plugins/servlet/applinks/listApplicationLinks \[atlassian.applinks.ui.BatchedJSONi18NBuilderFactory\] Duplicate i18n entry for key 'applinks.auth.provider.com.atlassian.applinks.api.auth.types.OAuthAuthenticationProvider'  
2018-03-20 17:36:15,735 http-bio-443-exec-15 ERROR adminconf 1056x15918x1 ecax3t 212.5.222.82 /rest/applinks/2.0/applicationlinkForm/manifest.json \[core.rest.ui.CreateApplicationLinkUIResource\] ManifestNotFoundException thrown while retrieving manifest  
com.atlassian.applinks.spi.manifest.ManifestNotFoundException: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure  
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1(AppLinksManifestDownloader.java:201)  
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.access$000(AppLinksManifestDownloader.java:44)  
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1$1.\<init\>(AppLinksManifestDownloader.java:86)  
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:79)  
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1.apply(AppLinksManifestDownloader.java:76)

and further up the stack:

Caused by: **javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure**   
at sun.security.ssl.Alerts.getSSLException(Unknown Source)  
at sun.security.ssl.Alerts.getSSLException(Unknown Source)  
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)  
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)  
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)  
at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)  
at sun.security.ssl.AppOutputStream.write(Unknown Source)  
at java.io.BufferedOutputStream.flushBuffer(Unknown Source)  
at java.io.BufferedOutputStream.flush(Unknown Source)  
at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:827)  
at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1975)  
at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993)  
at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397)  
at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)  
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)  
at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)  
at com.atlassian.sal.core.net.HttpClientRequest.executeMethod(HttpClientRequest.java:596)  
at com.atlassian.sal.core.net.HttpClientRequest.executeMethod(HttpClientRequest.java:546)  
at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:350)  
at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:161)  
at com.atlassian.plugins.rest.module.jersey.JerseyRequest.execute(JerseyRequest.java:141)  
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.download1(AppLinksManifestDownloader.java:150)  
... 194 more

On confluence side there is nothing probably because of high threshold for logs

It seems it still is related to the SSL layer?


author: Thomas Deiler
body: Yes - it is still SSL related.


Tags: jira