Issue links -> Wiki Page: You do not have permission to view this page

[Nabil Sayegh]

We've set up "Trusted Application" and "oAuth" between JIRA and Confluence. JIRA filters in Confluence work fine, but issue links from JIRA to Confluence are forbidden.

Any hint, how to configure these permissions?

[Nabil Sayegh · Accepted solution]

The application link was referring to the wrong context, i.e. the real address behind the reverse proxy. After deleting the link and recreating it with the configured context it works correctly.

[MartinS]

The documentation is wrong. It should not be:

If your (remote|local) application is Confluence, enter the following URL Patterns-
/plugins/servlet/streams,/plugins/servlet/applinks/whoami

But:

If your (remote|local) application is Confluence, enter the following URL Patterns 
   /plugins/servlet/streams
   /plugins/servlet/applinks/whoami
   /rpc/xmlrpc

[Raffi Enficiaud]

this solved my problem when linking issues from Jira to Confluence:

- in Confluence pages, I was able to see the Jira issues

- in corresponding Jira issues (eg. created directly in the Confluence pages), I had the following message: "You do not have permission to view this page". Also, when I was trying to link the Jira issue to a confluence page manually, under the drop down button "select a space", "Loading" was written without anything else, and all search results were empty.

So many thank! Adding the

/rpc/xmlrpc

solved all this.

However, still, in Sprint reports, when I click on "Linked page", I have the message

"No Confluence server is configured. Please check your Application Links configuration"

Any clue ?

I am using trusted authentication on both sides, I removed the OAuth. Using Jira 6.1.7 and Confluence 5.4.2, behind an NGinx proxy using SSL.

[MartinS]

Consider removing the URL Patterns completely. If you can life with the security implications, you will probably have a few problems less.

[Raffi Enficiaud]

Does not work. Any other clue?

[Raffi Enficiaud]

In the logs of NGinx I have this when I click on "linked issues" button on the sprint report (this feature used to work before, then I placed everything behind a webserver and updated the plugins):

10.42.1.16 - - [21/Mar/2014:18:12:27 +0100] "POST /confluence/rpc/xmlrpc HTTP/1.1" 200 4888 "-" "Jakarta Commons-HttpClient/3.0.1"
10.42.1.16 - - [21/Mar/2014:18:12:28 +0100] "POST /confluence/rpc/xmlrpc HTTP/1.1" 200 1544 "-" "Jakarta Commons-HttpClient/3.0.1"
10.34.28.115 - - [21/Mar/2014:18:12:28 +0100] "GET /jira/rest/greenhopper/1.0/sprint/3/pages?_=1395421947716 HTTP/1.1" 200 719 "https://atlas.is.localnet/jira/secure/RapidBoard.jspa?rapidView=1&view=reporting&chart=sprintRetrospective&sprint=3" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Firefox/27.0"

10.42.1.16 is the IP of the host machine, which is allowed in the trusted application, and 10.34.28.115 is my IP.

So it looks that the error message in incorrect in fact since something is sent to confluence, no?

[Raffi Enficiaud]

I solved the issue, due to a problem in the SSL certificate in fact: see

[https://answers.atlassian.com/questions/263207/linked-pages-between-agile-and-confluence?page=1#280833]

Now everything works fine again.

However, it would be nice to have proper warnings in the log files of JIRA, it would have saved me a lot of time.

[nikhil khedlekar]

Hi Nabil. I have the exact same problem. But I did not understand your solution below. Can you elaborate. "After deleting the link and recreating it with the configured context it works correctly."

[Nabil Sayegh]

BTW: Do I need oAuth at all, if I have configured Trusted Application bidirectionally?

[William Zanchet [Atlassian]]

Hey, I think that probably the account that was done the application links between Confluence and JIRA, don't have such privilegies to see this specific issue from JIRA.

[Nabil Sayegh]

The currently logged in used in JIRA is also currently logged in in Confluence and can see the page there. So it's not an individual permission problem.