Reverting from Crowd or JIRA to Internal User Management
If your Confluence site currently uses JIRA or Crowd for user management, you can revert to internal user management as described below. If your Confluence instance has only a few users, it is easier to recreate the users and groups in Confluence manually. If you have a large number of users and groups, it is more efficient to migrate the relevant users and groups into the Confluence Internal directory.
On this page:
Option 1 – Manually Recreate Users and Groups in Confluence
Use this option if you have only a few users and groups.
- Log in to Confluence as a Confluence system administrator.
- Go to the user directories administration screen and move the internal directory to the top of the list of directories, by clicking the arrows in the 'Order' column.
- Make sure that you have at least one user from the internal directory in each of the
- Make sure that you have a username in the internaldirectory with Confluence system administrator permissions.
- If you do not have such a user, add a new one now, and log out of Confluence.
- Log back in as the user you just added, and go back to the user directories administration screen.
- Disable the 'Atlassian Crowd' directory.
- Manually add the required users and groups in Confluence. They will be added to the internal directory, because you have moved it to the top of the list of directories.
- If you have assigned Confluence permissions to a group which exists in JIRA, you must create a group in Confluence with the same name.
- If a user who exists in JIRA has created content or has had permissions assigned to them in Confluence, you must also create that user in Confluence.
- Add the users to the required groups.
Option 2 – Transfer Crowd/JIRA Users and Groups to the Confluence Database
Use this option to migrate External Application (Crowd or JIRA) users into the Confluence database. You need a knowledge of SQL to perform this task.
The SQL commands given below are tailored for MySQL. If you are using a database other than MySQL, you will need to modify the SQL to work in your database.
Step 1. Create Backups
Creating backups is the only way to restore your data if something goes wrong.
- From Confluence, create a full XML site backup including attachments.
- Stop Confluence.
- Make a backup copy of the Confluence home and installation directories.
- Repeat the above steps for your External Application.
- From your MySQL administration tool, create a database backup for the Crowd/JIRA and Confluence databases.
Step 2. Replace Confluence User Management
Use the SQL below to move groups and users from your External Application to Confluence by transferring table content. The SQL provided is specific to MySQL and must be modifed for other databases.
Find the IDs for your Directories
Run the following command and take note of the resulting number. It will be referenced throughout the following instructions as <Confluence Internal ID>.
From the User Directories administration page, find the name of the directory who's users/groups you want to move. Run the following command and take note of the resulting number. It will be referenced throughout the following instructions as <External Application ID>.
Move Groups to Confluence
It is possible that you have several groups in your Internal Directory that have the same name as groups in your External Application. To find these, run:
If you have results from the previous query, for each of the group names that have duplicates, find the id for the group in the Confluence Internal Directory (<internal group id>) and the External Application (<external group id>). Run the following:
Move all the groups in the External Application to the Confluence Internal Directory.
Move Users to Confluence
It is possible that you have several users in your Internal Directory that have the same name as users in your External Application. To find these, run:
If you have results from the previous query, for each of the user names that have duplicates, find the id for the user in the Confluence Internal Directory (<internal user id>) and the External Application (<external user id>). Run the following:
Move all the users in the External Application to the Confluence Internal Directory.
Delete the External Application directory
- You need to change the order of your directories so that the Internal directory is at the top, and active.
If you have only two directories - the Internal and the External Application directory you are deleting, then do the following:
- If you have more than two directories, you need to rearrange them so the Internal Directory is at the top (list_index 0) and the External Application directory you are deleting is at the bottom.
List the directories and their order using
Change the list indexes so that they are in the order you want. Directory order can be rearranged using
- Check that the internal directory is enabled.
List the internal directory. An enabled directory will have its 'active' column set to 'T'
If the internal directory is not active, activate it by
When the directories are ordered correctly, delete the External Application directory from the directory order:
The External Application directory is referenced in several other tables in the database. You need to remove the remaining references to it:
All references to the External Directory should now have been removed. Delete the directory using:
- All users who were in the External Directory you deleted, including admins, will be unable to log in. Their passwords need to be reset by choosing the 'Forgot your password?' link on the login page. Alternatively, use the instructions at Restoring Passwords To Recover Admin User Rights to reset the administrator password, then set the users' passwords for them via the Manage Users page in the administration screen.
Was this helpful?
Thanks for your feedback!