Confluence returns "Unable to retrieve JIRA metadata" message in linked JIRA issues dialog when accessed by unlicensed users

XMLWordPrintable

    • 6
    • Severity 3 - Minor
    • 4

      Summary

      When unlicensed user from JIRA Service Desk access a space in Confluence and click on the JIRA issue dialog, Confluence returns the following error :

      atlassian-confluence.log throws the following error :

      2017-02-02 15:49:26,956 ERROR [JIRAMetadataPlugin:thread-9] [metadata.jira.helper.JiraMetadataErrorHelper] printError Unknown error encountered while retrieving JIRA metadata. Please check the logs.
– referer: https://jirajirajira/display/keykey/pagepagepage | url: /rest/jira-metadata/1.0/metadata | traceId: 39600d04bc6dc2d0 | userName: useruseruser
org.apache.http.client.ClientProtocolException
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:95)
at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:131)
at com.atlassian.applinks.core.auth.ApplicationLinkRequestAdaptor.executeAndReturn(ApplicationLinkRequestAdaptor.java:53)
at com.atlassian.applinks.oauth.auth.OAuthApplinksReturningResponseHandler.handle(OAuthApplinksReturningResponseHandler.java:45)
at com.atlassian.plugins.rest.module.jersey.JerseyRequest$2.handle(JerseyRequest.java:134)
at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:96)
at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:131)
at com.atlassian.applinks.core.auth.ApplicationLinkRequestAdaptor.executeAndReturn(ApplicationLinkRequestAdaptor.java:53)
at com.atlassian.applinks.oauth.auth.OAuthRequest.executeAndReturn(OAuthRequest.java:84)
at com.atlassian.applinks.core.auth.AbstractApplicationLinkRequest.execute(AbstractApplicationLinkRequest.java:114)
at com.atlassian.confluence.plugins.metadata.jira.service.JiraIssuesMetadataDelegate.getGroups(JiraIssuesMetadataDelegate.java:58)
at com.atlassian.confluence.plugins.metadata.jira.service.helper.SingleAppLinkMetadataHelper$2.call(SingleAppLinkMetadataHelper.java:133)
at com.atlassian.confluence.plugins.metadata.jira.service.helper.SingleAppLinkMetadataHelper$2.call(SingleAppLinkMetadataHelper.java:125)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.http.ProtocolException: Target host is not specified
at org.apache.http.impl.conn.DefaultRoutePlanner.determineRoute(DefaultRoutePlanner.java:70)
at org.apache.http.impl.client.InternalHttpClient.determineRoute(InternalHttpClient.java:124)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:183)
... 18 more
      Expected Behavior

      JIRA issue dialog returns warning message stating the user doesn't have permission, try log in with another user.

      Actual Behavior

      The error wasn't handled gracefully and no indication of the root cause was shown in the logs or UI.

        1. Screenshot from 2017-01-30 17-39-23.png
          Screenshot from 2017-01-30 17-39-23.png
          24 kB

            Assignee:
            Unassigned
            Reporter:
            Jonathan Soo
            Votes:
            14 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: