Topic
  • No replies
pyost
pyost
1 Post

Pinned topic UCM Activity doesn't keep Owner history

‏2013-11-06T18:41:43Z |

ClearCase 7.1.2 on AIX with authentication through ldap; ClearCase Remote Client on Windows.

We recently had a developer and a team lead leave the company.  Both user accounts were removed from AIX, but a new account was created that re-used the "ldap id" of the developer. (To explain this further, the developer's login id was con21009 and the corresponding "ldap id" was 2042, i.e., when the developer was still here, the aix command 'lsuser con21009' would show "con21009  id=2042" etc.  The new account that was created re-using the same ldap id number is for user id con21466.)

Now, when viewing UCM activities for a stream from the Remote Client, the Owner column for activities that were owned by the former developer (con21009) shows the new user id, con21466, which is using the common ldap id.

In the same view from Remote Client, activities that were owned by the former team lead, cob01045, now show "UNIX:UID-545" in the Owner column, where 545 is the "ldap id" of her old account.

However, issuing the 'cleartool lsact' command for the stream displays the correct owner information, i.e., the old user ids, con21009 and cob01045, of the former developer and team lead.

Is there any way to change the behavior within CCRC to display the same information that is displayed from the command line rather than interpreting the current ldap id information?

Thanks in advance for any help or insight!