The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Migration steps from Confluence ondemand to hosted with Crowd w/AD

John Plut
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 5, 2014

We have an ondemand Confluence site. We are bringing it in house. I understand if we get the usernames matched up, the content should be attributed to the AD user after restoring it from a backup. (Is this true??) If so what are the steps?

There are a few things to do, but I need to know what order. A few of the steps would be

  • Import data from ondemand site (do this before or after joining Confluence to Crowd/AD?)
  • Rename users to match AD usernames (do this before or after joining Confluence to Crowd/AD?)
  • Rename groups to match AD groups (do this before or after joining Confluence to Crowd/AD?)

Is there an up to date Doc for the username rename process. I beleave I saw Jira has this built in to the interface now?

Thanks

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 6, 2014

You can rename users in latest versions of Confluence too. Just administer the user to do that. But renaming groups is not possible. My suggestion would be to rename users and use same groups. Steps would be:

1. Import data from onDemand to in-house

2. Rename users to match AD

3. Create matching groups in AD and add users to those groups

4. Connect to AD via Crowd and make sure the Crowd directory is placed ahead of internal user directory

TAGS
AUG Leaders

Atlassian Community Events