Mission Critical Issue
When a JIRA issue is inserted into a Confluence page via the JIRA Macro, instead of using the Display URL as defined in the Application Link settings (https://[JIRA-PublicURL]:8443), the link displayed in the page uses the Application URL (localhost:8080).
This error completely defeats the purpose of using JIRA and Confluence together. None of the links to JIRA issues work. 1) Inbound traffic to port 8080 is closed on our firewall, 2) localhost cannot be resolved to our JIRA-PublicURL's IP address, and 3) all traffic must come in over HTTPS to port 8443 in order to securely access JIRA.
Any help would be greatly appreciated.
I see that this issue has existed with previous versions with Confluence and the JIRA Macro (and there were some fixes/updates applied to the JIRA Macro for it to work), but this issue still persists with the most recent version of JIRA Macros (v 5.1.3).
FYI1: I tried rolling back to the latest 4.x version of the JIRA Macro to no avail. Linking would not work at all.
FYI2: The Public URLs for both Confluence and JIRA above are the same as their respective Base URL setting.
JIRA v 6.0.7, Confluence v 5.3 with JIRA Macros v 5.1.3 installed.
Applications are linked via localhost connection.
I submitted a ticket earlier, and Atlassian support also directed me to the same link. Support agreed that Confluence 5.3 is also experiencing this bug, and as of today (2013-10-31), they inserted the Conf 5.3 version into the list of affected versions.
We need this fixed, otherwise,
this: [Confluence collaboration] <-linking between-> [JIRA issues]
Inbound traffic to port 8080 is closed on our firewall, 2) localhost cannot be resolved to our JIRA-PublicURL's IP address, and 3) all traffic must come in over HTTPS to port 8443 in order to securely access JIRA.
Then why are you trying to use localhost:8080? You're saying this is blocked specifically by your firewall, but where is the firewall? I'm assuming confluence and jira are installed on the same server but if the firewall is also located on the server, then those ports and addresses would be blocked. Why not use the display url for both application and display url if those ports and addresses resolve correctly?
We are using localhost:8080 because of the below:
JIRA and Confluence are on the same machine. They communicate via Application Link behind the firewall over their respective, unsecured ports (8080 and 8090), and this Application Link seems to work fine.
We originally tried to create the Application Link between the two via their respective SSL ports (8443 and 8444). However, Confluence and JIRA cannot connect to each other for some reason. I think the reason they cannot connect via SSL has something to do with the fact that we are using self-signed certs, but I'm not really sure, mainly because we did these steps:
1) the hosts file has both JIRA-PublicURL and Confluence-PublicURL resolving to 127.0.0.1, and
2) both self-signed certs have been added to the root CAcerts keystore so that the JIRA and Confluence instances will trust the self-signed certs.
Because Application Links via SSL wouldn't work (after trying practically every tip found in all the online documentation, Q&A on this forum, and the currently known issues and workaournds that we could find, and then banging our head on the wall for about a solid week), we are having to resort to unsecured communication via localhost:8080 and 8090 for the application URL, and this allows the Application Link to function correctly, which the JIRA Macros addon needs. This communication is behind our firewall anyway, so we decided is OK for JIRA and Confluence to communicate unsecured via localhost.
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...
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!
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