Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

ApplicationPermissionException error when integrating Crowd into Jira as a user directory

Joe Bennett March 28, 2019

I am having trouble integrating atlassian crowd as a directory for jira. Both of them are behind an ELB, using HTTPS on both ends. To the instances I use a self-signed cert which is handled by nginx which acts as a reverse-proxy so that I can do ssl.

I used https://confluence.atlassian.com/jirakb/integrating-jira-with-nginx-426115340.html and https://confluence.atlassian.com/crowdkb/how-to-use-nginx-to-proxy-requests-for-crowd-416583345.html. To set it up with both of them.

The error I get when I try to test out connection to a Crowd application definition from jira is
```Connection test failed. Response from the server:
com.atlassian.crowd.exception.ApplicationPermissionException: HTTP Status 403 – ForbiddenType Status ReportMessage Client with address "127.0.0.1" is forbidden from making requests to the application, jira.Description The server understood the request but refuses to authorize it.Apache Tomcat/8.5.34```


The remote address in crowd is set to the CNAME of jira's ELB.

1 answer

1 accepted

0 votes
Answer accepted
Joe Bennett March 29, 2019

I found the solution, 127.0.0.1 needs to be in the `Remote addresses` tab of the application configuration in Crowd.

Suggest an answer

Log in or Sign up to answer