I am unable to set the FishEye JIRA/Crowd Authentication Settings - what am I doing wrong?

I want to be able to use the same set of users already configured in JIRA for FishEye/Crucible.

I have created a completely trusted Application Link in JIRA with FishEye/Crucible. Its name is 'fisheye'.

Using FishEye Administration, when I open Authentication Settings and attempt to Edit the FishEye JIRA/Crowd Authentications this error always displays:

"Problem communicating with JIRA: Application failed to authenticate"

The FishEye JIRA/Crowd Authentication Settings are:

Authenticate against: a JIRA instance

Application Name: fisheye

Aplpication password: *******

JIRA URL: http://jiraserver:8080

Auto-add: Create a FishEye user on successful logon

Peridoically synchronise users: Yes

Synchronise Period 1 hour

When synchronise happens: Copy new users and changes...

[SSO is disabled]

Can anyone shed some light onto why this might be happening?

4 answers

1 accepted

0 votes
Accepted answer

Hi David,

I don't think this is related to different number of users.

The error:

"Problem communicating with JIRA: Application failed to authenticate"

indicates that FishEye can't communicate with JIRA. So I would recommend you to double check the connection for user management created at JIRA USER SERVER. Maybe the url or even password is not correctly set. You could also refer to this article for more information:


Anyways, you're welcome to visit support.atlassian.com and open a support ticket attaching the application logs so we can perform a deeper investigation of this issue.


Leonardo Macedo.

Many thanks Leonardo - this has solved my problem, but perhaps not as you imagined. When I checked back to the JIRA User Server page (which I haven't looked at for a while), all the application names had been changed!

Instead of 'fisheye' the name was now 'FishEye - localhost - BF03DB78-9822-4269-AE38-A2944847633E' (confluence and bamboo had also been changed in a similar fashion!)

Luckily, the 'fisheye-users' group which I had set up earlier (with a sub-set of 5 members) was still there, so I just re-added that in FishEye administration now that the two applications are communicating with each other again.

I have no idea how this was changed, although I have been upgrading all Atlassian applications over the last month and have had a few issues with Application Links. All I can imagine is that something I did during the JIRA upgrade must have resulted in the changes to the JIRA User Server application names.

Interesting - these upgrades have been fun.

Hey David,

Well observed! This could definitely be related to FishEye/JIRA upgrade. I did see something like that last week but I didn't realize could have changed with upgrade.

Thanks for your feedback.



Is it possible that this behaviour is present because we only have a 5-user licence for FishEye/Crucible whereas we have a 10-user licence for JIRA?

But what does that mean ??? This should not be this hard -

If either of fisheye or jira has "FishEye - localhost - 4c84f7d3-bfdd-31a4-8676-bb1fdbc2d527"

then I get this mumble-jumble on fisheye:

Problem communicating with JIRA: <!DOCTYPE html> <html> <head> <title>Forbidden (403)</title> <!--[if IE]><![endif]--> <script type="text/javascript">var contextPath = '';</script> <link type="text/css" rel="stylesheet" href="http://localhost:8080/s/en_US-3kuvpj/786/3/1/_/download/superbatch/css/batch.css" media="all"> <!--[if lt IE 9]> <link type="text/css" rel="stylesheet" href="http://localhost:8080/s/en_US-3kuvpj/786/3/1/_/download/superbatch/css/batch.css?conditionalComment=lt+IE+9" media="all"> <![endif]--> <!--[if IE 9]> <link type="text/css" rel="stylesheet" href="http://localhost:8080/s/en_US-3kuvpj/786/3/1/_/download/superbatch/css/batch.css?conditionalComment=IE+9" media="all"> <![endif]--> <!--[if lte IE 9]> <link type="text/css" rel="stylesheet" href="http://localhost:8080/s/en_US-3kuvpj/786/3/1/_/download/superbatch/css/batch.css?conditionalComment=lte+IE+9" media="all"> <![endif]--> <link type="text/css" rel="stylesheet" href="http://localhost:8080/s/en_US-3kuvpj/786/3/e95a49780a3d091005957684ce055976/_/download/contextbatch/css/atl.general/batch.css" media="all"> <link type="text/css" rel="stylesheet" href="http://localhost:8080/s/en_US-3kuvpj/786/3/c03802a4af1811c54fcadfd5e15918af/_/download/contextbatch/css/jira.general/batch.css" media="all"> <link type="text/css" rel="stylesheet" href="http://localhost:8080/s/en_US-3kuvpj/786/3/4d4c84bfede8756172afcbde337d7b29/_/download/contextbatch/css/jira.global/batch.css" media="all"> <link type="text/css" rel="stylesheet" href="http://localhost:8080/s/en_US-3kuvpj/786/3/1.0/_/download/batch/jira.webresources:global-static/jira.webresources:global-static.css" media="all"> <link type="text/css" rel="stylesheet" href="http://localhost:8080/s/en_US-3kuvpj/786/3/1.0/_/download/batch/com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources/com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources.css" media="all"> <!--[if lt IE 9]> <script type="text/javascript" src="http://localhost:8080/s/en_US-3kuvpj/786/3/1/_/download/superbatch/js/batch.js?conditionalComment=lt+IE+9" ></script> <![endif]--> <script type="text/javascript" src="http://localhost:8080/s/en_US-3kuvpj/786/3/1/_/download/superbatch/js/batch.js" ></script> <!--[if lte IE 8]> <script type="text/javascript" src="http://localhost:8080/s/en_US-3kuvpj/786/3/1/_/download/superbatch/js/batch.js?conditionalComment=lte+IE+8" ></script> <![endif]--> <script type="text/javascript" src="http://localhost:8080/s/en_US-3kuvpj/786/3/1/_/download/superbatch/js/batch.js?cache=false" ></script> <script type="text/javascript" src="http://localhost:8080/s/en_US-3kuvpj/786/3/e95a49780a3d091005957684ce055976/_/download/contextbatch/js/atl.general/batch.js" ></script> <script type="text/javascript" src="http://localhost:8080/s/en_US-3kuvpj/786/3/c03802a4af1811c54fcadfd5e15918af/_/download/contextbatch/js/jira.general/batch.js" ></script> <script type="text/javascript" src="http://localhost:8080/s/en_US-3kuvpj/786/3/4d4c84bfede8756172afcbde337d7b29/_/download/contextbatch/js/jira.global/batch.js" ></script> <script type="text/javascript" src="http://localhost:8080/s/en_US-3kuvpj/786/3/1.0/_/download/batch/com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources/com.atlassian.administration.atlassian-admin-quicksearch-jira:admin-quicksearch-webresources.js" ></script> <script type="text/javascript" src="/rest/api/1.0/shortcuts/786/bd65079ca439b8740a285c3dddb9fcd4/shortcuts.js"></script> </head> <body id="jira" class="aui-layout aui-style-default page-type-message"> <div id="page"> <header id="header" role="banner"> <nav class="global" role="navigation"> <div class="primary"> <h1 id="logo"><a href="/secure/MyJiraHome.jspa"><img src="/images/jira111x30.png" width="111" height="30" alt="Innovations Labs" /></a></h1> </div> </nav> </header> <section id="content" role="main"> <header><h1>Forbidden (403)</h1></header> <div class="content-container"> <div class="content-body"> <p>Encountered a <code>403 - Forbidden</code> error while loading this page.</p> <p><a href="/secure/MyJiraHome.jspa">JIRA home</a></p> </div> </div> </section> </div> </body> </html>


This was very helpful. I had the same problem after our last JIRA upgrade. For some reason there where 2-3 Jira User Server users for fisheye and crucible in JIRA. I deleted all of them in JIRA. In Fisheye Admin I removed the JIRA/Crowd Integration under Authentication.

Then to re-create the jira authentication, I followed the instructions on this link https://confluence.atlassian.com/display/FISHEYE/JIRA+and+Crowd+Authentication

Cliff Notes version:

  1. In Jira, create a new user for Fisheye under JIRA Users Server
  2. In Fisheye, setup the JIRA\Crowd integration under Authorization using the new user you just created

Thanks again for this post!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,711 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you