Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Hello All
We have JIRA and Fisheye/Crucible both on HTTPS
Initially we configured App link Between them with the OAuth authentication method and it worked successfully but now it is giving error 500.
OAuth option in Application Link wizard not visible for JIRA for both Incoming and Outgoing Authentication.
It is available in Fisheye/Crucible for Incoming Authentication but for Outgoing Authentication it is throwing bellow error.
An Application Link from the remote application to this application is required to configure this authentication provider.
Application Link 'JIRA' was created successfully locally but the reciprocal link was not created.
In JIRA on view issue page under review and source tab following error was thrown
javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
Is it related to SSL certificate??
can anybody explore how to configure SSL with
JIRA - Fisheye/Crucible
both application have same JAVA version.[1.7]
I have been fighting this issue myself recently. You need to add the Fisheye key to the keystore on the JIRA server and the JIRA key to the keystore on the Fisheye server.
See this for more information.
https://confluence.atlassian.com/display/DOC/Running+Confluence+Over+SSL+or+HTTPS
Hi Rahul,
This definitely points to an SSL error. We have a couple of KB Articles on resolving SSL errors. If you find that you're still unable to create the application link I'd recommend creating a support ticket to resolve the issue.
It seems like this may be related to SSLv3 "banning" that happen in Java 7u76.
I am experiencing the same error described in the original question trying to link to JIRA 6.3.15 front ended by apache from Confluence 5.7.4 running on Java 7u80.
http://mail.openjdk.java.net/pipermail/security-dev/2015-January/011667.html
So...you may need to look at this: http://www.go2group.com/2015/07/21/troubleshooting-series-linking-multiple-atlassian-applications-with-sslv3/ Ties into SSLv3 banning as was mentioned before.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreHey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.