I think this is a bug, but I want to be sure I have not missed some obscure configuration setting first.
I am running JIRA v5.0.1 and Confluence v4.1.3 with a shared username authentication managed by Crowd.
I have set up Application Links both ways between JIRA and Confluence.
I have set up Project-specific Application Links in JIRA to specific Spaces in Confluence.
Inserting a JIRA Issue using the Atlassian-provided macro in a Confluence page correctly displays the JIRA Issue information in the page, and provides a correctly functioning link to that issue. In the selected JIRA Issue, in the "Issue Links" section of the Issue display, it correctly references that the Wiki Page mentions the Issue, however it wrongly tells the user they do not have permission to see the page, even though they do have correct permissions. This is illustrated in the screen shot:
Ah. Apparently in addition to having to manually list all of these URLs in the Trusted Applications pane:
One must also add this one:
So, the Atlassian documentation wrong, as it does not list all of those URLs. And the Application Links technology is poorly designed, as it should itself add the correct URLs during configuration.
Christopher, thanks very much! I have been looking for the reason of my JIRA/Crucible integration not working for a while and re-did the whole HTTPS / app link configuration from scratch a few times ... and I had the problem you mention from the start! I would have never found the solution if it wasn't for this last reply! And guess ... no mention of these paths in Atlassian documentation!!
The JIRA log shows nothing at all for this problem.
The Confluence log displays this single message:
2012-05-17 11:23:46,514 WARN [http-443-1] [auth.trustedapps.filter.TrustedApplicationFilterAuthenticator] authenticate Failed to login trusted application: jira:3540274 due to: com.atlassian.security.auth.trustedapps.InvalidCertificateException: Request not allowed to access URL: /rpc/xmlrpc
Ok, so since I have Application Links set up, and they were configured without error, what does this mean? How do I fix it?
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