Error: Sorry, there are no links available when using anonymous access, check the permission configuration of the remote application.

meena radhakrishnan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 3, 2012

Everything was working fine between JIRA and Crucible all of a sudden not sure what has changed the JIRA ticket ids are no longer linked within Crucible. When checked noticed that the project link is missing on Crucible side to JIRA's project. When I tried to link Crucible's project to JIRA's I get the following error.


"Enter link details:

Sorry, there are no links available when using anonymous access, check the permission configuration of the remote application."


Fisheye window has the following:

rojects-v1"]
012-05-04 08:03:50,876 WARN - Authentication failed for application link MP
JIRA (45a22524-cb76-35fc-bf44-6567d0c2948d) http://test-srv-36:8080 com.atl
ssian.applinks.application.jira.JiraApplicationTypeImpl@1344f5a. Response heade
s: {WWW-Authenticate=OAuth realm="http%3A%2F%2Fvm-srv-36%3A8080", Set-Cookie=at
assian.xsrf.token=BOSA-LRJ6-1OTA-HEPI|29627251b8040a0f794f710552c0f0bf936c3f21|
out; Path=/, X-Seraph-Trusted-App-Error=BAD_URL; Request not allowed to a
cess URL: {0}; ["/rest/applinks/1.0/permission/create-entity/69337696-3f8a-37a0
9b00-9fca39332477"], X-AUSERNAME=anonymous, Connection=close, Server=Apache-Coy
te/1.1, X-Seraph-LoginReason=OUT, Cache-Control=no-transform, Transfer-Encoding
chunked, Date=Fri, 04 May 2012 12:03:50 GMT, X-Seraph-Trusted-App-Status=ERROR,
Content-Type=application/json;charset=UTF-8, X-AREQUESTID=483x435x1} body: {"st
tus-code":401,"message":"Client must be authenticated to access this resource."

The application links between Crucible and JIRA use 'Trusted application' mode. Am I missing something here?

thanks

4 answers

1 accepted

3 votes
Answer accepted
meena radhakrishnan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 9, 2012

Dropping and recreating the application links resolved this issue.

Dina Goncharenko April 27, 2017

Thank you for posting your solution...saved me a ton of time!

2 votes
jhgorse September 6, 2012

If running behind an Apache mod_proxy, try adding your Apache proxy's IP to trusted IP Patterns under the JIRA/Confluence Application link configuration.

Alagu Meena A February 21, 2013

Hello, I am too facing the same problem , when I try to link JIRA project from Crucible Application, I got the same error.

"Sorry, there are no links available when using anonymous access, check the permission configuration of the remote application."
"

I can able to add Crucible projects from JIRA application.

This is the error from the Crucible Logs.

2013-02-06 01:06:14,340 WARN [btpool0-1828 ] com.atlassian.applinks.core.rest.PermissionResource com.atlassian.applinks.core.rest.PermissionResource$4-handle - Authentication failed for application link Enterprise Jira (471e9df5-bad0-3680-9002-a1d57e598afd) https://jira.sabre.com com.atlassian.applinks.application.jira.JiraApplicationTypeImpl@6dd36d8f. Response headers: {WWW-Authenticate=OAuth realm="https%3A%2F%2Fjira.sabre.com", Date=Wed, 06 Feb 2013 07:06:14 GMT, Content-Length=4417, Set-Cookie=JSESSIONID=03CC236399CEE8A65068BA2973D68DC8; Path=/; Secure; HttpOnly, Content-Type=text/html;charset=UTF-8, Connection=close, X-Seraph-LoginReason=AUTHENTICATED_FAILED, X-AREQUESTID=66x2092869x1, Server=Apache, X-Content-Type-Options=nosniff} body: <!DOCTYPE html>

https://jira.sabre.com has siteminder integration. JIRA Crucible Integration uses Basic Authentication. Can you please suggest what could be the reason.

1 vote
IGS November 10, 2013

I just wanted to add that clock skew (~ 34 seconds worth between confluence and jira servers) was causing this issue for us.

Manually triggering an ntpdate and ensuring both machines have ntpd enabled appears to have solved this.

0 votes
Jamie Saunders March 12, 2013

Logging out of my user account and back in solved the problem for me.

Suggest an answer

Log in or Sign up to answer