Do I need 1:1 license for Jira and Confluence when listing Jira content with the Jira Issue macro?

Question

We have a 500 cal Confluence license and a 100 cal JIRA license.

We would like the Confluence users to be able to list JIRA content, e.g. a list of issues that was resolved in the last version, without needing a JIRA license.

I'm unable to get this to work for Trusted Apps, Oauth (with and without impersonation) and Basic access. Users that have a user in both systems will be able to log in and see the information with Trusted Apps and OAuth without impersonation (assuming they authenticate in the last example). If the logged in user in Confluence do not have a user in Jira, this error message is shown (this is expected as I understand that Trusted Apps need the same user in both systems):

JIRA Issues Macro: The JIRA server returned a trusted apps error: PERMISSION_DENIED;	Permission Denied;	[]

With impersonation/OAuth or Basic Access, it fails with the following:

JIRA Issues Macro: JIRA project does not exist or you do not have permission to view it.

I have created a user for this in JIRA, and within JIRA that user can run the same query and get the result. So the user and access rights work just fine - but somehow it fails when we cross the border between the two systems.

Shouldn't I be able to use Basic Access for this, or at least OAuth with impersonation

Ivar · Answer

I assume the user configured on Confluence side shouldn't have access to all Jira projects, only the project we want to enable the content on. And yes - all the others are, or should be, in place already. I've logged an issue with Atlassian support on the matter as it doesn't seem to work as it should.

Jobin Kuruvilla [Adaptavist] · Answer

You should be able to do that. No need for 1:1 licenses.

If you go with basic access, make sure the user configured on Confluence side has access to all JIRA projects. If it is OAuth, make sure the JIRA user who is mapped to the Conf user has the required access.

Ivar · Answer

Based on this page, https://confluence.atlassian.com/display/DOC/JIRA+Issues+Macro, I should: "If the outgoing authentication is set to Basic Access, people can see the JIRA issues that are visible to the user account configured in JIRA's outgoing authentication setting."