JIRA Internal directory cleanup after Crowd migration

Question

good day team,

We use JIRA and Confluence with the current setup:

* JIRA's user/group directory: internal directory
* Confluence's user/group directory: JIRA internal directory

We are about to deploy Crowd and shift user/group management from Jira/Confluence local to Crowd. However, we want to keep the JIRA/Confluence local directories enabled and only populated with a local admin account.

My question is: assuming that the migration goes well and Crowd becomes the sole user/group management entry point, how could we clean up the JIRA and Confluence internal directories (suppressing all users and only keeping the local admin account) ?

In advance, Many thanks for your feedback,

Cheers, Fred

Frederic Baud · Answer

Hi Noam,

Thanks for your prompt feedback. The part of the migration you mention is well understood and controlled.

The reason behind the local directories cleanup is as follow:

* we want to keep the local directories enabled and populated only with a local admin account
* we want to delete all originally defined end users to prevent security holes and also if the Crowd platform was to go down, not allow anyone to log in through an internal directory that would be out-of-date

That's why, post migration, we really want to cleanup the local directories from all end-users defined in Crowd.

And I am yet to figure out how to get this done.....

Cheers, Fred

noamdah · Answer

Fred,

As long as the user names of all your users are the same all you need to do is add the crowd directory into JIRA, after the full sync of users just up the priority of the new directory.

Once the crowd directories priority is at the top of the list all the users will work form the crowd.

(All the comments, assigned issues, etc.. will be on the new user)(Must have the same username)

After or before you do this you can create a new admin use and make sure that the username is not the same as any user coming from crowd.