Cannot connect bitbucket cloud organisation to jira server

Menno van den Ende

I cannot connect jira server to bitbucket cloud.

When trying to connect i receive the following error:

The authentication with Bitbucket has failed. Please check your OAuth settings.

I've checked the team account name, OAuth Key and Secret 10 times, and i'm 100% sure they are correct.

I've checked the atlassion-jira.log and found the following error:

2018-08-29 13:06:12,629 http-nio-8080-exec-3 WARN balticode 786x49775x1 h4dbnl [some ip adresses here] /secure/admin/AddBitbucketOrganization.jspa [c.a.j.p.d.s.bitbucket.webwork.AddBitbucketOrganization] Error redirect user to bitbucket server.
java.lang.IllegalArgumentException: Response body is incorrect. Can't extract a token from an empty string

A little bit of searching on google resulted in this link. However, when looking at my server configuration, timezone is set correctly and synced with NTP, see screenshot: http://prntscr.com/ko7kdx

What else could be wrong? Using jira software 7.11.0

Thanks in advance!

Shannon S

Menno,

Are you behind a proxy by any chance? If so, if you bypass the proxy does the issue persist? You can also try putting Jira in Safe Mode to see if an add-on is causing the issue.

For the workaround is there a way to manually sync it to double-check?

Lastly you can try recreating the OAuth consumer:

1. Log in Bitbucket using the the right team or user account

2. From Bitbucket settings -> OAuth, Revoke the JIRA access -> Delete the existing JIRA OAuth consumer

3. Add a new OAuth consumer as follows:

   • Name: any name
   • Callback URL: http://jira:8080 (Jira URL)
   • Grant ALL Permissions
   • Save

4. Use the new tokens for adding DVCS Account in JIRA

---

If the problem persists, follow these steps to enable debug logging so that we can have more visibility on what happens in the backend:

1. From JIRA, go to JIRA Administration -> System -> Logging and Profiling

2. Click Configure logging level for another package

3. Add org.apache.http as package name -> Leave logging level as TRACE -> Add

4. Click Configure logging level for another package (again)

5. Add com.atlassian.jira.plugins.dvcs as package name -> Leave logging level as TRACE -> Add

6. Add the DVCS Account again for JIRA to log the DEBUG messages

7. Generate a fresh Support Zip

Once you have that, I can make a support ticket for you so you can send it to us and we can investigate.

Regards,

Shannon