Fisheye recent changeset gadget and source tab empty when Anonymous read access is disabled for the repository

I've followed the guide below and both JIRA and Fisheye users are using LDAP authentication.

https://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+FishEye

But the recent changeset JIRA gadget is empty and the source tab is empty when I disable anonymous read access to the respository. I don't want anonymous access for the repository, how do I get JIRA to integrate with Fisheye when anonymous access is disabled?

1 answer

1 accepted

0 votes
Answer accepted

This is a bug in the Application Link when the application is not using the default port 443 for HTTPS:

Please try the following workaround:

  1. Stop FishEye/Crucible
  2. Edit FishEye/Crucible <tt>config.xml</tt>and add a proxy port setting to force the port to 8440:
    &lt;web-server site-url="https://fisheye:8440"&gt;
    		&lt;http bind=":8441"/&gt;
    		&lt;ssl keystore-password="Sanitized by Support Utility" bind=":8440" truststore-password="Sanitized by Support Utility" truststore="C:\cert"&gt;
    			&lt;proxy-info proxy-port="8440"/&gt;
    		&lt;/ssl&gt;
    	&lt;/web-server&gt;
  3. Restart FishEye/Crucible and try again

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Opsgenie

Getting the Most out of Atlassian and Opsgenie Together

We’re excited to invite you to this action-packed webinar where we will demonstrate how to integrate Opsgenie’s powerful alerting and on-call management tools with your entire Atlassian stack. Mar...

67 views 0 1
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