Unable to search for Jira issues from Confluence or Confluence Pages from Jira
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Symptoms
From JIRA:
Can't search for Confluence pages to link to JIRA issues
Existing links show: "You do not have permission to view this page"
From Confluence:
Can't search for JIRA issues to include in Confluence pages
Existing links show: "JIRA issue doesn't exist or you don't have permission to view it"
The following appears in the atlassian-jira.log:
1
2017-02-24 21:54:23,826 http-nio-2786-exec-3 WARN admin 1314x277x2 rf4lxg 192.168.1.100,192.168.1.100 /rest/applinks/3.0/status/e87b0b73-eaa1-3493-bc27-a5bd27a7de29 [c.a.a.i.migration.remote.TryWithCredentials] You do not have an authorized access token for the remote resource.The following appears in the atlassian-confluence.log:
1
2
2017-02-24 21:53:51,093 WARN [http-nio-2782-exec-2] [internal.migration.remote.TryWithCredentials] execute You do not have an authorized access token for the remote resource.
-- referer: http://andynguyen.vn/cfl/admin/listapplicationlinks.action | url: /cfl/rest/applinks/3.0/status/b2693708-529b-3dda-804b-9c1a6d3e78e5 | traceId: a41148e6656babee | userName: adminDiagnosis
JIRA and Confluence are running behind a proxy, using the same domain (same VirtualHost) with different context paths. For example:
http://andynguyen.vn/jira
http://andynguyen.vn/cfl
Cause
The VirtualHost for the domain in the proxy config contains this parameter: RequestHeader unset Authorization.
If JIRA and Confluence use different domains (different VirtualHosts), the parameter doesn't take effect and the problem doesn't happen.
Solution
Resolution
Remove the parameter RequestHeader unset Authorization from the VirtualHost config and restart the proxy.
Was this helpful?