Reassociating Users
Pre-requisites:
To reassociate a user through the CentraSite Command Line Interface, you must have the CentraSite Administrator role.
Before you run the tool, create a database backup.
In addition to the database backup, make sure the following conditions are satisfied:
There is a unique registry object for the old external user.
The old external user can be uniquely identified in the security configuration.
There is no registry object for the new external user.
There is no security configuration for the new external user.
The domain of the new external user exists in the security configuration.
A GUI configuration does not exist for the new external user.
You can change the association of a CentraSite user from one external user to another. This can be necessary, for example, if the responsibility for certain CentraSite assets moves from one person to another person in the same authentication domain. By reassociating the user, you can keep the name of the CentraSite user unchanged. Another possible use would be to handle user IDs when the default domain name changes; for example, when switching from operating system authentication to LDAP authentication.
CentraSite provides a Java tool named ReassociateUsers.jar for this purpose.
The tool automatically grants the new external user the same permissions that were granted for the old external user.
Run the Java tool ReassociateUsers.jar. Given the user ID:
C:\SoftwareAG\CentraSite\utilities>CentraSiteToolbox.cmd ReassociateUsers.jar <CentraSite URL> <admin user id> <password> users <old user id> <new user id>
Given the domain ID:
C:\SoftwareAG\CentraSite\utilities>CentraSiteToolbox.cmd ReassociateUsers.jar <CentraSite URL> <admin user id> <password> domains <old domain id> <new domain id>
Given the user mapping details:
C:\SoftwareAG\CentraSite\utilities>CentraSiteToolbox.cmd ReassociateUsers.jar <CentraSite URL> <admin user id> <password> file <user mapping file path>
The input parameters are:
Parameter | Description |
CentraSite URL | The URL of the CentraSite registry. For example, http://localhost:53307/CentraSite/CentraSite. |
admin user id | The user ID of a registered CentraSite user who has the CentraSite Administrator role. For example, Administrator. |
password | The password for the CentraSite user identified by the parameter admin user id. |
old user id | The domain ID of the old external user. |
new user id | The domain ID of the new external user. |
user mapping file path | The absolute or relative path to the user mapping file. If relative, the path should be relative to the location from where the command is executed. The user mapping file contains a map of key-value pairs, and defines the user objects as simply lines of comma separated old user and new user pairs (for example, "OLDDOMAIN\oldUser, NEWDOMAIN\newUser"). Note: | The same user ID must not be specified more than once in the mapping file. |
|
The reassociation may take some time. The tool’s progress is reported to standard output.
Examples (all in one line):
C:\SoftwareAG\CentraSite\utilities>CentraSiteToolbox.cmd ReassociateUsers.jar http://localhost:53307/CentraSite/CentraSite DOMAIN\admin pAsSw0rD users OLDDOMAIN\oldUser NEWDOMAIN\newUser
C:\SoftwareAG\CentraSite\utilities>CentraSiteToolbox.cmd ReassociateUsers.jar http://localhost:53307/CentraSite/CentraSite DOMAIN\admin pAsSw0rD domains OLDDOMAIN NEWDOMAIN
C:\SoftwareAG\CentraSite\utilities>CentraSiteToolbox.cmd ReassociateUsers.jar http://localhost:53307/CentraSite/CentraSite DOMAIN\admin pAsSw0rD file users.txt
