We have a JIRA and Confluence server installed on the same machine. For about a year we've used the internal user management systems for each. I would now like to transition to using the JIRA user management system for both.
I followed the instructions for Connecting Confluence to Jira applications for User Management
However, I receive the following error after I click "Test Settings" in Confluence's Configure Atlassian JIRA Server. I made sure that the JIRA user server has an entry for Confluence, and I've tried both the local (127.0.0.1) and the public IP.
Configure Atlassian JIRA Server - Confluence Connection test failed. Response from the server: com.atlassian.crowd.exception.ApplicationPermissionException: Forbidden (403) Encountered a "403 - Forbidden" error while loading this page. client.forbidden.exception Go to JIRA home
Searching for previous solutions brings me to this page.
I followed the instructions, except I don't understand "configure http://127.0.0.1:port/context_path on the "Server URL" settings." What is "context_path"?
I have tried using http://127.0.0.1:8080/ and http://127.0.0.1:8080/jira but both return the following error:
Configure Atlassian JIRA Server - Confluence Connection test failed. Response from the server: The following URL does not specify a valid Crowd User Management REST service: http://127.0.0.1:8080/rest/usermanagement/1/search?entity-type=user&start-index=0&max-results=1&expand=user
I can provide screenshots if necessary.
Thanks!
What is the path you use to access JIRA?
Are you using a proxy?
What is the OS of the server?
Are you running a firewall on the server?
We have a URL mapped to the public IP of the server that JIRA & Confluence are installed on. Is that what you mean by path used to access JIRA?
We are running Linux.
I'm not sure on the proxy and firewall questions. I've reached out to the person that runs the server to ask.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you heard anything about firewall or proxy configurations?
Do you have an application link between Confluence and JIRA setup?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for the delay. I'm dealing with multiple time zones.
There is no proxy set up. We are using a firewall (iptables).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have an application link setup between confluence and jira?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes. In JIRA admin under User Management > JIRA user server > Add application I added confluence. For the IP addresses I tried the public IP address for the machine as well as 127.0.0.1
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Matthew,
Couple of things to check as this does not sound like a network/proxy/firewall issue.
I am hoping that you just missed white listing your application or the JIRA user server is not configured correctly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First, I want to thank you for working through this with me.
Second, I double checked, and all of the steps you suggested were done correctly.
Finally, I have actually gotten it to work, but the solution is incredibly confusing to me. The IP that I use when I set up the JIRA user server (Admin > User Management > JIRA user server) is the IP that we use to access JIRA and Confluence (mapped via a URL, of course). When I change the IP to X.X.X.* then my error goes away. Why would this wildcard get rid of the 403 error message?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Matthew,
I am not a routing expert but my guess it has something to do with how the request is being routed and by using the wildcard you are able to get through. You could run a trace and see.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'll work with our server admin on the issue.
Let's go ahead and mark this issue as solved.
Thanks for all your help Brant!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm running jira as cluster for 2 nodes.
I'm using the following config for jira user server.
I added the 2 IPs of the 2 server nodes (.4 - .5) as follows in the IP addresses section:
::1
172.29.1.5
172.29.1.4
127.0.0.1
And also I can confirm that the url that I access confluence from is whitelisted (already done successfully the application link between jira and confluence).
But the following error persist while testing:
Connection test failed. Response from the server:
com.atlassian.crowd.exception.ApplicationPermissionException: Forbidden (403) Encountered a "403 - Forbidden" error while loading this page. client.forbidden.exception Go to Jira home
Waiting for your kind response and help.
Thank you in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have similar situation,
created link, two way between jira and confluence
In my case, both jira and confluence run behind nginx and ssl termination.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
me too (
any solutions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.