Our confluence instance (6.15.10 server) is connected to active directory. We are moving to a new active directory server. The only thing that is changing between severs is the actual hostname or so I am being told by our network team.
Do I need to just modify the existing user directory hostname in confluence to the new hostname? Or do I need to Add a new directory?
I checked the knowledgebase and I see where it give instructions on how to edit the existing active directory settings, but I was concerned with if these edits will have any impact to existing users/permissions. If I edit the existing active directory - will this have any impact to current users and any confluence permissions assigned through confluence and not AD.
Thanks for any input. And if this is documented somewhere in the knowledgebase, please point me in that direction!
A direct edit of the hostname/ip address should work here if everything else is staying the same. Once done, synchronized the directory again.
For safety my suggestion would be
This is the safer way to go.
Advantage of the first way where you are just changing hostname over the second is if a user is mapped to a local group, you do not need to add them to the local group.
My group is looking to do something similar.
If I use the 1st method and just type in a different hostname/IP address; it will retain all of the Confluence content as long as I resync the directory. Am I understanding this correctly?
If I use the 2nd method, does this retain all my local groups? We have a lot of local groups with different rights; and I don't want to reassign groups. Will it retain all of my confluence content?
Why is the 2nd method safer compared to the 1st method?
That is correct @Kim-Viet Le
If the directory has a different username and password you have to account for this. My assumption is the new directory has the same configuration and structure as the old. The only difference is that you are moving to something new.
If you have an issue say users complain they don’t have specific access after your change, you can easily change the directory order and Jira behaves as it used to.
Secondly, if you have totally different configurations(different user filter, group filter, membership attributes), you will need to change these for the first to work however once you have changed it, if you didn’t save what it used to look like, a rollback becomes a real pain.
With the second, I just need to change the directory order and the application will behave as it used to.
The biggest draw back with the second is you need to reassign any local group membership because Jira uses directory Id to map membership to groups in the database.
Hi, Confluence collaborators! As part of #Confluence-Collaboratory month, we’ve created a very special Mythsbusters segment, where we're dive into an interesting myth and uncover the truth behind i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events