i'm experiencing a problem accessing to our self-hosted Confluence and JIRA Instances.
In our company, we suddenly changed our network addresses of all computers and virtual machines running, including those of Confluence and JIRA.
Now Confluence doesn't let me login because cannot contact our Crowd directory due to an invalid IP address; Crowd directory is the JIRA instance.
I tried to change some IP addresses inside Confluence database, unfortunately nothing changed.
Falling back to our last domain addresses is not an option at this time.
How can I change Crowd directory IP address correctly?
Thanks in advance,
I hope you rolled back any changes you made in the Confluence database.
It sounds from your description as if you can still log into Jira. You may only need to add the new Confluence IP to the application configuration in Jira User Server. For instructions, please see: Allowing connections to JIRA for user management
If that fails, you may use the internal Confluence directory to log into Confluence and edit/recreate the User Directory settings for the connection to Jira. I am not sure what version of Confluence you are running but this doc has the latest instructions, and links out to the documentation for the older versions: Restore Passwords To Recover Admin User Rights
For more background on how User Directories work in Confluence, you might find this useful: Managing Multiple Directories
I welcome any follow up questions and look forward to hearing how it goes.
thanks for your quick reply!
You're right, I've have full access to JIRA instance and I finally managed to get logged into Confluence instance, enabling again internal user directory of Confluence from database.
What's blocking me now is JIRA and Confluence are not talking with each other; I found a configuration inside JIRA (Admin Panel -> User management -> JIRA server user) which still contained the the old/wrong IP address of Confluence.
Before changing this property, connection attempts from JIRA to Confluence always got the answer: "Error 403 - Forbidden" (inside Confluence logs).
After changing, JIRA connections to Confluence are still not working but the exception changed: "Failed to authenticate application", as if Confluence is now able to reach JIRA instance but unable to authenticate.
Where should I Iook at now?
Thanks Leonardo, that was useful to know the message in the log changed once you added the new Confluence IP to the application configuration in Jira User Server
Reset the application password over in Jira User Server and then re-enter it in Confluence in the Jira ("Crowd") User Directory setup. Any error in the UI when you save the configuration could be helpful.
if that doesn't help:
Create a new application for Confluence in Jira User Server (in Jira) and then add a new User Directory in Confluence to connect to Jira using the new application credentials.
I hope to hear good news from you soon.
Good morning Ann,
I tried your suggestions and finally got Confluence connecting correctly to JIRA through User Directories test feature, I changed application name and password used to connect to each other.
If I disable Confluence internal directory and enable JIRA remote directory directly on Confluence database ('cwd_directory' table), restart Confluence instance and try to login to Confluence, I'm not able to connect; error on Confluence log is:
"<user> tried to login but they do not have USE permission or weren't found."
...as if there's no user available, although the user exists inside JIRA internal directory and is a member of correct groups (jira-users, confluence-users, jira-developers).
I can't understand if JIRA receive a login request from Confluence with that user or what..
Sounds really frustrating.
Do you use templates with Confluence? Take part in a remote 1-hr workshop. You'll receive USD $100 for your time! We're looking for people to participate in a remote 1-hr workshop...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs