Trusted communication between JIRA and Confluence

I just upgraded Jira and Confluence to the latest version. One of the new features of this upgrade is the ability to set up trusted communication between Jira and Confluence. Our users were able to add and edit JIRA Issues and JIRA Portlet macros, but they were needed to include a username and password in the macro markup code. No one wanted to use own credentials, so I created the generic account for this exercise. There was a great possibility of data leak from any JIRA project. New trusted communication feature allows Confluence to request information from JIRA on behalf of the currently logged-in user without providing username and password.

I followed the instructions on Atlassian site, but when I tried to actually add JIRA Issues Macro without username and password. I got the following very unclear message on Confluence page:
Errors were reported by the JIRA trusted connection.
* Invalid certificate

In the same time this error message appeared in Jira's catalina.out log file
WARN [atlassian.seraph.filter.TrustedApplicationsFilter]
Failed to login trusted application: confluence:14618160 due to:
com.atlassian.security.auth.trustedapps.InvalidCertificateException:
confluence:1425183460 cause:
com.atlassian.security.auth.trustedapps.InvalidRemoteAddressException: 127.0.0.1

So I added 127.0.0.1 address to the "IP Address Matches:" list of the JIRA's trusted application configuration, but I was still getting the same message on Confluence page errors were reported by the JIRA trusted connection.
* Invalid certificate

Somehow I figured out that now it could be a caching issue. I navigated to 'Cache statistics' in Administration, and flushed all the caches by selecting 'Flash all' link. Finally JIRA Issues and JIRA Portlet macros work with trusted communication between Jira and Confluence

No comments: