nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Destination User Directory has moved

Malachi Burke_0qaupf

I've moved JIRA which Confluence is using for a User Server from one IP address to a local DNS name (jira.xxxx.net). Now the Remote JIRA Directory can't connect, and users are no longer synchronized. I've spent about an hour trying to fix it, with no luck. How can I repair this connection?

I realize variations of this question have been asked and answered, but they are an overwhelming collection of Q&A, SQL commands, rollback recommendations and frankly I get lost.

Accepted answers

All comments

AnnWorley

Hi Malachi,

I understand you changed the Jira URL from an IP address to a DNS name. Since then Confluence has not been able to connect to Jira for user management.

Please let me know what steps you have taken and what error messages you are seeing in the browser and the logs:

Have you edited the Jira URL in the User Directory in Confluence? Please see these instructions if not: Connecting Confluence to JIRA applications for User Management
Please check the <confluence_home>/logs/atlassian-confluence.log for errors connecting to Jira. Note: The <confluence_home> directory is the path defined in the following file: <confluence_install>/confluence/WEB-INF/classes/confluence-init.properties.

The log should have errors indicating that the external user directory is not available during authentication. The error messages should give us a clue as to why it isn't connecting.

I look forward to hearing more about your case.

Thanks,

Ann

AnnWorley

edited

Malachi Burke_0qaupf

At the point where I try to "Add" "Atlassian JIRA" in the Confluence User Directory area, I get a :

'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'

Even though I triple-checked that Application Name and Application Password match

Here are some screenshots:

AnnWorley

Thanks for the screen shots. Based on those:

You need to log in with an administrative account from the Confluence Internal Directory so you can edit the Remote Jira directory.
Then you have the 403 error to overcome.

Internal Administrator

For logging in with an internal admin, go to Confluence Admin>Groups and check the membership of the confluence-administrators group. If you do not have credentials for a user in that group, then add a user (it will add them in the Confluence Internal directory unless the Jira directory is read/write)and add the user to the confluence-administrators group so they will be a super user.

Then you can edit the existing Remote Jira user directory to point at the DNS name instead of an IP address.

Eliminating 403 Forbidden connecting to Jira

You will likely see the same 403 error when connecting with the existing user directory that you are seeing when adding a new Jira user directory. To get connected, please see: Unable to connect to JIRA for authentication - Forbidden 403

Confluence server could not connect or access to JIRA server due to the following cause:

JIRA does not include Confluence server IP address in JIRA User Server settings
JIRA has not whitelisted Confluence server or IP address, despite both of them located within same server.
There is a proxy or firewall that blocks such access from Confluence to JIRA.

Please try the resolutions from the article and let me know if you see any other error when connecting to Jira for user management.

Malachi Burke_0qaupf

For the Internal Administrator guidance, the account I am logged in as reports to being a member of the confluence-administrators group. I am able to attempt adding remote JIRA user directories, as indicated in 2nd screenshot (Confluence_userdirectory_2)

For the Eliminating 403 guidance:

Item 1

In the 3rd screenshot (JIRA_userdirectory_1) I have IP address specified of 192.168.0.0/16 to allow all traffic in from 192.168.x.x which does match our IP range

Item 2

I added a whitelist entry (http://wiki.moducom.net) but unfortunately no change.

Item 3

Also, I don't see how a proxy or firewall could be blocking it - BUT - there is indeed an nginx reverse proxy in place forwarding:

jira.moducom.net -> localhost:8080
wiki.moducom.net -> localhost:8090

It works well enough for other areas (such as application linking).

How do you recommend we proceed?

Malachi Burke_0qaupf

Thank you for this.

In regards to your initial Recommendation, if the only way forward is to specify a direct IP and port instead of a proxy, I will do it. However, that's what got me into this trouble in the first place, and I would much prefer the mobility of an actual DNS name.

In regards to the Secondary recommendation, I would like to do this; however it's a bit of a chicken and the egg, I am not able to add any more users to Confluence - presumably because Confluence is hard-wired to be a "slave" to JIRA users as you can see in the screenshot below. What would you recommend to enable an internal administrator account in this situation?

AnnWorley

I mistakenly assumed your Jira user directory was read-only. Confluence creates the user in the first directory it has permission to write to, in this case the Jira user directory because it is on top. It fails because it can't connect currently. (I was able to reproduce the behavior on my test instance after making the Jira User directory read/write.)

Please move the Internal Directory up in the order and then create the internal admin. For more on how the directories work see: Managing Multiple Directories

Back to the 403 error: Can you ping or nslookup and resolve the DNS name of the Jira server from the command line on the Confluence server? What if you do a traceroute to that IP? Does it go through any network devices that could be blocking the connectivity?

Malachi Burke_0qaupf

Following these instructions, I was able via direct IP address to set up a 2nd JIRA user directory reference (disabling my first one) and successfully synchronize. Thank you immensely for this.

Regarding utilizing DNS naming:

JIRA DNS ping and nslookup work quite well from the command line on the Confluence server.

JIRA DNS reference for aforementioned 2nd JIRA user directory works if "http://jira.moducom.net:8080" is specified. That is a little unexpected, because the proxy is, as mentioned before, arranged to do jira.moducom.net:80 -> [::]:8080 and definitely does exactly that during normal usage.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira