Best practice for old directories after migrating to Crowd

I recently implemented Crowd for JIRA, Confluence, and Fisheye/Crucible.  This involved moving three directories (2x LDAP and the internal directory) from each JIRA and Confluence into the same three directories in Crowd.  At this point I plan on deleting the old delegated LDAP authentication directories from JIRA and Confluence as the users coming from Crowd just naturally override the old users.

However, the internal directory is a more complicated issue as it cannot be deleted.  In JIRA, I can move the Internal directory higher than the Crowd directory and then delete the Internal directory users one by one (I plan on leaving an administrative account in case of emergencies).  This is not ideal by any means, but it works to clean up old data.

I cannot do the same in Confluence.  I moved the Internal directory higher than the Crowd directory, but I get errors deleting users "because he or she has authored content in one or more spaces".  This seems like an artificial error in this case because I was able to remove two whole directories full of users who have authored content and that content was simply mapped to the new user record from Crowd.

What have others done to clean up old data after migrating to Crowd?  I really don't want to leave old data sitting around as it only serves to complicate the solution.

1 answer

You really need to leave an admin user in JIRA and Confluence internal directory in case the link between Application and Crowd is not working.

You could move the Crowd directory in first position.
Run a query in database to indenty all users that are in internal and in Crowd directory and do nothing with these users.
And identity all users in internal and not in Crowd, should only stay the admin user account.

Regards

Yes, I planned on leaving at least one admin user in the JIRA and Confluence internal directories for recovery purposes.

However, doing nothing with the overlapping users doesn't resolve my original complaint that there is now a lot of duplicated data that only serves to complicate the current situation. This will only get worse over time as some accounts get disabled in Crowd but don't get changed in the no-longer-used internal directory.

It would be really nice if Atlassian had a whitepaper to cover the migration to Crowd that included some more complicated scenarios (e.g. moving multiple directories to crowd) and included what to do with the data that is no longer needed in JIRA and Confluence.

As far as resolving my issue with the extra internal users that are no longer needed, it seems like there are no options outside of fixing the data directly in the database.

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

595 views 2 15
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot