Any way to change user ID?
Is there any GUI interface to change user ID without directly update the database tables? Thanks.
If we 'have to' manually update the database tables, what tables should be updated? It seems that there are two tables (CONTRIBUTOR*) contain the actual user IDs (e.g. first.m.last) and other tables refernces the internal IDs for each user account, but I did not check all tables. Could anyone please tell me which tables should be updated?
I understand it is not recommended to manually update the DB tables directly, but a project has some users whose IDs do not match their enterprise ID and thus cannot be LDAP authenticated. The project does not want to create new RTC accounts for these users and then re-assign existing work items.
If we 'have to' manually update the database tables, what tables should be updated? It seems that there are two tables (CONTRIBUTOR*) contain the actual user IDs (e.g. first.m.last) and other tables refernces the internal IDs for each user account, but I did not check all tables. Could anyone please tell me which tables should be updated?
I understand it is not recommended to manually update the DB tables directly, but a project has some users whose IDs do not match their enterprise ID and thus cannot be LDAP authenticated. The project does not want to create new RTC accounts for these users and then re-assign existing work items.
One answer
There is no way to change the userIds. It's also not easy to directly
modify the DB tables, because (1) the table/column names are generated
on install and might very from install to install, and (2) the userId is
designed to be non-changing, so there might be other references to the
userId that would not be properly updated if you were to try a direct DB
modification.
Additionally, the DB tables you were referring to only holds the
queryable data for a Contributor. The 'real' copy of the Contributor
data is stored in a blob in a different table that would be very hard to
update like you want.
I can understand the desire to avoid the work of creating second
accounts for people who got their IDs mixed up, but that will really be
the only way to ensure that you system stays in a consistent state. If
somebody is willing to invest time in a tool that helps solve the
problem (as you hinted at modifying the tables directly), then a good
direction to go would be to write a tool that helps ease the pain of
creating new users and re-assigning bugs instead.
-
Matt Lavin
Jazz Server Team
On Thu, 2008-11-20 at 06:37 +0000, yanli wrote:
modify the DB tables, because (1) the table/column names are generated
on install and might very from install to install, and (2) the userId is
designed to be non-changing, so there might be other references to the
userId that would not be properly updated if you were to try a direct DB
modification.
Additionally, the DB tables you were referring to only holds the
queryable data for a Contributor. The 'real' copy of the Contributor
data is stored in a blob in a different table that would be very hard to
update like you want.
I can understand the desire to avoid the work of creating second
accounts for people who got their IDs mixed up, but that will really be
the only way to ensure that you system stays in a consistent state. If
somebody is willing to invest time in a tool that helps solve the
problem (as you hinted at modifying the tables directly), then a good
direction to go would be to write a tool that helps ease the pain of
creating new users and re-assigning bugs instead.
-
Matt Lavin
Jazz Server Team
On Thu, 2008-11-20 at 06:37 +0000, yanli wrote:
Is there any GUI interface to change user ID without directly update
the database tables? Thanks.
If we 'have to' manually update the database tables, what tables
should be updated? It seems that there are two tables (CONTRIBUTOR*)
contain the actual user IDs (e.g. first.m.last) and other tables
refernces the internal IDs for each user account, but I did not check
all tables. Could anyone please tell me which tables should be
updated?
I understand it is not recommended to manually update the DB tables
directly, but a project has some users whose IDs do not match their
enterprise ID and thus cannot be LDAP authenticated. The project
does not want to create new RTC accounts for these users and then
re-assign existing work items.