Changing the Jazz User ID Using the RTC Plain Java Client Libraries

Recently there were several forum posts about changing the user ID used by JTS and the Jazz products RTC, RQM, RRC to authenticate them against the authentication realm like LDAP, or Tomcat based authentication. In some scenarios this is simply required to change a mistyped user ID while keeping the users association to the Jazz artifacts. Some scenarios are more complex. For example switch to a new LDAP system and changing the user ID.

The general approach is described in this tech note. Following the tech note you can use the administration UI to change the ID. If you need to completely switch the LDAP system and the new system has new user ID’s you have to take some more things into consideration.

  1. Switch off the LDAP sync task, while you do the changes. Otherwise it might sync the new users with the different ID’s in.
  2. You will need an administrative user after switching to the new system. Make sure you create one in the old system that conforms to the ID’s in the new system, or have one or more additional administrative accounts and change them to a valid new ID in the new LDAP system.
  3. You can change all the other user ID’s in the current system or the new system. Consider to keep the admin ID for the old system as long as you are testing.

In Doors Next Generation this is not supported. See for work arounds.

Doing all the user ID changes manually might be tedious and error prone. It will also take time. While you do it, the system might not be available for the users.

Changing the user ID this way only changes the ID in the Jazz databases. You need to make sure to provide a matching user ID in the user registry you are using. If you just want to change the user ID’s and not change the registry, make sure to modify the user ID’s in the registry to match the user Jazz user ID.

If you run Tomcat and its built in registry, managing the ID’s in the file Tomcat/conf/tomcat-users.xml, you need to change the value of the property username to match the ID in the Jazz database. Shut down the server, change the property for the users to match their Jazz user ID, save the file and restart the server.

Yesterday, in a discussion with a team of RTC users that is currently looking into changing the LDAP system and all their user ID’S, the question about automation came up. I could not resist and looked into an opportunity to have more automation for this task. It turned out to be almost trivial to code up some tool that can help with the effort and allows to

  • Simulate the user ID change, testing the input file and the user ID’s in the first column, but don’t change an ID.
  • Run the user ID change, change the user with the ID provided in the first column to the ID provided in the second column.

Lets look at how that would work.

License and how to get started with the RTC API’S

As always, our lawyers reminded me to state that the code in this post is derived from examples from as well as the RTC SDK. The usage of code from that example source code is governed by this license. Therefore this code is governed by this license, which basically means you can use it for internal usage, but not sell. Please also remember, as stated in the disclaimer, that this code comes with the usual lack of promise or guarantee. Enjoy!

If you just get started with extending Rational Team Concert, or create API based automation, start with the post Learning To Fly: Getting Started with the RTC Java API’s and follow the linked resources.

You should be able to use the following code in this environment and get your own automation or extension working.

To keep it simple this example is, as many others in this blog, based on the Jazz Team Wiki entry on Programmatic Work Item Creation and the Plain Java Client Library Snippets. The example in this blog shows RTC Client and Common API.


The complete Eclipse project with the code is available as download here.

Solution Overview

The code contains two classes.

  1. ChangeUserID is the main class that needs to be called
  2. CSVFileReader is a utility class that helps with reading the input file


Please consider to test this in a test environment and create a backup before you try this on a production repository. In contrast to using the UI there is no protection against changing the ID. You don’t have to enable it and you don’t have to switch the property User Registry Type from LDAP to UNSUPPORTED. If you run the command with an administrative user with parameter true your ID’s will be changed. You can seriously damage your environment if you do something wrong.

How to use the tool

You need to import the sources into Eclipse and provide the plain java client libraries as described in this article, in order to be able to run it. In this case a sample launch comes with the code. Alternatively you can compile the example code and provide the plain Java Client Libraries in the classpath.

Call ChangeUserID.main with parameters repositoryURI AdminUserId AdminPassword InputFileName performModification where performModification is true or false. The input file referenced by InputFileName needs to be a CSV file with at least two columns and ‘,’ as separator. The first column is the current user ID, the second the desired new user ID.

For example call it with these parameters for simulation

"" user password "C:\temp\modifyIDs.csv" false

Call it with these parameters to perform the changes

"" user password "C:\temp\modifyIDs.csv" true

Please be aware that the context root jts is not a typo. You want to change the users in JTS, which promotes the changes to all the other applications. Please check that the uid’s have been changed in the registered applications after running the tool.

The input file needs to have a compatible format as described above: It needs to be a CSV file with at least two columns and ‘,’ as separator. The first column is the current user ID, the second the desired new user ID. This would be a valid example:


You can have additional columns and the tool will ignore them. The tool also makes sure that the original user ID exists and the new user ID is not empty. White space characters around the user ID’s  will be removed.

If your file is using a different separation character, you can modify the constant below at the beginning of the class ChangeUserID to fit your needs.

private static final String SEPERATOR = ",";

Is there automation to retrieve the user list?

As a starting point, you can run a repotools-jts command against your repository. The following command will provide you with a CSV file containing all the users in the repository:

repotools-jts -exportUsers toFile=userlist.csv repositoryURL=https://:/jts/ adminUserId= adminPassword=

The resulting text file has the right format. All you need to do is to add a new column that contains the new ID’s. I tried this with our Open Office based Symphony spreadsheet editor. The following steps worked for me:

  1. Start Symphony
  2. Select File>Open
  3. Browse for the file and open it
  4. Review the settings and make sure the separator is correct, the default worked for me
  5. Finish the import

Once the file is in the spreadsheet editor, just click on the second column and add a column. You can add the new ID’s and keep the other columns in the file for easier user recognition and editing. You could potentially do the same with a test repository that has imported all the users of the new LDAP system. Maybe using some spreadsheet magic such as sorting helps you to use cut and past to get the new ID’s into the new column.

If you use Symphony you want to make sure to open Tools>Instant Corrections, switch to the Options tab and disable at least the option capitalize fist letter on every sentence if your ID’s start with a lower case letter. The image below shows an example screen shot.

file Edit user table

While editing the file, keep in mind, if you leave out the new user ID, the ID will not be changed. The tool does also not change the ID of the admin that runs the command.

After you are satisfied you can simply save the CSV file with Symphony.

I tried the same procedure with MS Excel and there are some issues.

  • Excel by default wants a TSV file. It wants to use a tab as separator. You can change this if you use the Data>Import option instead of opening the file directly
  • Excel writes the file as Colon Separated Values file using ‘;’ and not tab or a comma. Either fix this behavior or change the SEPARATOR constant in ChangeUserID

The API Code Explained

I am not going to try to explain all the code that is needed to get the data to be able to do the ID change in detail. It is simply trying to open a file, read it line by line, analyze the data and call the interesting API code with it.

The change of the user ID is done in the operation ChangeUserID.changeUserID() shown below. The code is really simple.

 * Find the user ID and change to the new user ID. doUpdate = false does
 * simulation only. In simulation mode: Try to locate the contributor by
 * user Id but do no change.
 * @param teamRepository
 * @param originalID
 * @param newID
 * @param doUpdate
 * @throws TeamRepositoryException
public static void changeUserID(ITeamRepository teamRepository,
		String originalID, String newID, Boolean doUpdate)
		throws TeamRepositoryException {
	System.out.print("Set user: " + originalID + " to " + newID
		+ (doUpdate ? "" : " - Simulation"));
	IContributor user = teamRepository.contributorManager()
		.fetchContributorByUserId(originalID, null);
	IContributor contributorWorkingCopy = (IContributor) user.getWorkingCopy();
	if (doUpdate) {
			contributorWorkingCopy, null);
	System.out.println(" - OK");

The code simply uses the current user ID provided to fetch the contributor. If the contributor can be found it gets a working copy. If not in simulation mode, it sets the new ID and saves the working copy. The operation throws an exception in case the user with the original ID can not be found. This is caught in the calling method and displayed e.g. to be able to fix the input file.

The downloaded code has basic error handling and also works for malformed input files. However, you might want to extend it a bit for general usage. You should definitely consider using a test system to make sure your data is correct and you can use the system after you did the changes.

Well, writing the tool was less than an hour. Commenting and blogging took 4 times as much, so I hope this is useful for the readers and saves some poor guy with a huge user base some time.

27 thoughts on “Changing the Jazz User ID Using the RTC Plain Java Client Libraries

  1. Hi Ralph,
    Great post!. The tool will for sure make life easier in some situations 😉
    Thanks for this very helpful contribution!
    Best Regards,

  2. Hi Ralph,
    Tried the code on my test environment. I was able to understand how it works using the knowledge gained in your previous post.
    Very well explained and a good example.


  3. Pingback: Maintaing User Photos With the Plain Java Client Libraries | rsjazz

  4. Hi Ralph,
    On a local installation (RTC 3.0 with no external registry), the change worked fine except for these two abnormalities (I know this post is to help with LDAP external registries, I’m simply commenting for others interested):
    -the user’s lost their Jazz server roles, and
    -their passwords have been reset to the new User ID’s value.

    After fixing the server role with an RTC admin user, I was able to successfully log on with the new user IDs and their new passwords, they seemed to have access to the same artefacts. I’ll let you know how it goes when we’ll do our tests against a test LDAP.

    • Paul, was that on Tomcat? If so, you would have to make sure the tomcat-users.xml (shut down tomcat before changing it) has the ID’s that are desired. I tried that with Tomcat and it worked well for me. If you ran into issues, please, if you find out the root cause, let me know what happened.

      • Tomcat = yes. Root cause still unknown. Our next step is to test with the external LDAP test registry next week and see if we observe the same behaviour.

      • Hi Ralph,

        we tried it on one of our test environment.

        The user IDs were changed as explained but the jazz repository permissions of the users were lost.

        Can you please let me know how to proceed at this point.

        Best Regards,

      • The repository role mapping is done by the LDAP system. If the user does not show a repository role any more the following things might be true
        – Not changed back registry type from UNSUPPORTED to LDAP
        – Incorrect User ID not matching LDAP recored.

      • Hi Ralph,

        The Repository setting were set to LDAP.

        And I see the below warning

        The user roles could not be retrieved: CRJAZ1231E The following user could not be found in the external user directory: “test.sbx3″ID CRJAZ1527E

        Many Thanks,


      • Hello Ralph,

        So, we need to change the user-id in LDAP as well before executing this script.

        I will explain what exactly happened.

        We have created 5 test users with user-id’s as below.,,,,

        Changed these user id’s to below using the script.


        All the users were renamed as explained. But when once the LDAP is synchronized. It created the users again now we have all the below users in CLM.


        Can you please help us in how to avoid LDAP to create the users again.

        Many Thanks,

        Best Regards,

      • I think I mentioned in the post to disable LDAP sync before you do that.

        The other thing is that you obviously need to change the ID’s in LDAP first, and the IDS in LDA and in Jazz must match before you enable LDAP sync again. The ID is what is used in the LDAP sync to determine if a user already exists.

    • I can not comment on product roadmaps and futures of these products.

      I would not bet on it. The blog does use the built in capabilities. All it does is to provide more automation for a border case that should happen almost never.

      So you can do it today and here is more automation. There are likely more pressing enhancement requests. If you think this should be provided in the product I would suggest to open an enhancement request.

  5. Hi Ralph, we are currently testing this procedure.

    We found a problem on DOORS after following your guide, every artefact history missed the “Editor Name” and “Created By”. Does this guide works for all CLM softwares?

  6. Hi Ralph,

    First, let me just say your blog is great!

    I implement migration application. It will copy item revisions and tasks from legacy system into RTC change sets and RTC work items.
    I would like to maintain ownership between tools, so it looks like created in RTC by same people as in legacy systems. Let’s assume users have already been created in RTC.

    Is there a better way to assign ownership other than re-logging in RTC with other credentials and then putting in RTC some object for this user, than re-login to put something for another user?


  7. Hello Ralph,

    this should become part of “repotools-jts” like “-createuser”. Unfortunatly repotools can only modify user attributes and create new users, but not rename userID.


    • Hi Guido, I am not sure you want to expose this in repotools, as it can be dangerous and you could lock you out of the system if you do something wrong. You can file an enhancement request however.

  8. Hi Ralph,

    After changing the user-id, reports related to the users are not visible.

    When the user login and click on My Reports in JRS, the list is empty.

    When we check in All reports could find them. But only the Public reports.

    Reports saved as Private are not visible anywhere.

    Is there any way to resolve this issue.

    Many Thanks,

    Best Regards,

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.