Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Handshake error trying to connect Jira Server to Bitbucket Cloud

wtriplett
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 24, 2018

Hi, I am trying to connect Jira 7.7.1 Server to Bitbucket Cloud team account, and am getting an error. I've entered the Account/Team name correctly, and added the OAuth key/secret from bitbucket.

The error shows up on the Jira web interface as "Error! Invalid Team/User Account"

In the catalina.out, there's this:

2018-12-24 07:37:40,057 http-nio-127.0.0.1-8080-exec-15 INFO mememem 457x97x1 x9ybe4 10.17.3.225,127.0.0.1 /secure/admin/AddBitbucketOrganization.jspa [c.a.j.p.d.s.b.clientlibrary.request.BaseRemoteRequestor] Failed to execute request: https://bitbucket.org/api/1.0/users/myteam- Received fatal alert: handshake_failure

At one point this worked because we had the linkage set up properly, but synchronization started failing at some point along the way.

Things I've Tried:

Upgrading to latest Jira in dev/testing environment - same error
Added bitbucket.orgs certificate to the cacerts file and restarted Jira based on web advice

Thanks in advance

1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
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.
December 24, 2018

A "handshake error" usually means there is something wrong with the SSL certificates you are using.  My guess would be that Bitbucket is on SSL and you have not imported the certificates into your Jira system correctly.

Have a look through https://confluence.atlassian.com/kb/ssl-and-application-link-troubleshooting-guide-719095282.html

wtriplett
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 24, 2018

Thank you - that link was very helpful. Ultimately I needed to the below entry in $JIRA_HOME/bin/setenv.sh to TLSv1.2 as opposed to TLSv1. I also did a lot of other things prior to that, like add the intermediate certificates to the cacerts truststore file in the jvm, but ultimately this is what worked.

#
#  Occasionally Atlassian Support may recommend that you set some specific JVM arguments.  You can use this variable below to do that.
#
JVM_SUPPORT_RECOMMENDED_ARGS="-Djdk.tls.client.protocols=TLSv1.2"

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events