Delete manual user entry from LDAP managed user registry
This has hindered us from importing the user from LDAP and there appears no way around this. The LDAP nightly sync does not appear to have addressed this either.
We get the error below when trying to import:
Problem occurred during user import
CRJAZ1317I User with the same user id "xxxxx@uxxxx.com" already exists.
existing user: "com.ibm.team.repository.common.model.impl.ContributorImpl@336c336c (stateId: , itemId: , origin: <unset>, immutable: true) (contextId: , modified: 2010-03-30 19:54:34.468, workingCopy: <unset>) (mergePredecessor: null, workingCopyPredecessor: <unset>, workingCopyMergePredecessor: <unset>, predecessor: null) (emailAddress: xxxxx@uxxxx.com, userId: xxxxx@uxxxx.com, name: User Name, archived: false)"
new user: "com.ibm.team.repository.common.model.impl.ContributorImpl@60876087 (stateId: null, itemId: , origin: <unset>, immutable: <unset>) (contextId: , modified: null, workingCopy: true) (mergePredecessor: null, workingCopyPredecessor: <unset>, workingCopyMergePredecessor: <unset>, predecessor: null) (emailAddress: xxxxx@uxxxx.com, userId: xxxxx@uxxxx.com, name: XXXX X. xxxxxxxx, archived: false)"
Is there a way to correct this via the application or do we need toremove the user directly from the database?
Also, if we are using LDAP as a user registry, why would the "Create User" button be enabled on the web ui?
9 answers
We had inadvertently added a user to RTC using the Create User button in the web UI and now we cannot find the user in our server to make any corrections.
This has hindered us from importing the user from LDAP and there appears no way around this. The LDAP nightly sync does not appear to have addressed this either.
We get the error below when trying to import:
Problem occurred during user import
CRJAZ1317I User with the same user id "xxxxx@uxxxx.com" already exists.
existing user: "com.ibm.team.repository.common.model.impl.ContributorImpl@336c336c (stateId: , itemId: , origin: <unset>, immutable: true) (contextId: , modified: 2010-03-30 19:54:34.468, workingCopy: <unset>) (mergePredecessor: null, workingCopyPredecessor: <unset>, workingCopyMergePredecessor: <unset>, predecessor: null) (emailAddress: xxxxx@uxxxx.com, userId: xxxxx@uxxxx.com, name: User Name, archived: false)"
new user: "com.ibm.team.repository.common.model.impl.ContributorImpl@60876087 (stateId: null, itemId: , origin: <unset>, immutable: <unset>) (contextId: , modified: null, workingCopy: true) (mergePredecessor: null, workingCopyPredecessor: <unset>, workingCopyMergePredecessor: <unset>, predecessor: null) (emailAddress: xxxxx@uxxxx.com, userId: xxxxx@uxxxx.com, name: XXXX X. xxxxxxxx, archived: false)"
Is there a way to correct this via the application or do we need toremove the user directly from the database?
Also, if we are using LDAP as a user registry, why would the "Create User" button be enabled on the web ui?
We are having the same problem
If the user has done work, you might want to think about fixing the user ID and e-mail to match LDAP so that the current user is in sync with LDAP and will stay that way in the future.
Comments
Darshan, I would suggest to open a separate question. Trying to ask about a completely different topic in an ongoing question does not make sense and usually does only confuse readers of the thread.
If you managed to get JTS and CCM out of sync e.g. due to a inconstistnet restore from a backup (see https://jazz.net/wiki/bin/view/Deployment/BackupCLM ), you will likely not be able to recover from that without reaching out to support.
Hi Ralph, Aplogies for this. But if i understand this correctly then this post also talks about deleting the users from LDAP managed user registry. We also want the same thing. We saw Clement Liu (Nationwide) commented that they did some changes in WAS console and deleted the users which resolved their problem. We just wanted to know what exact changes are needed.
Comments
Each application JTS, CCM, QM (not RM) has its own user managment. JTS syncs the users to the other apps. You would have to try to connect to CCM and try to get rid of a user. You could try to use the Technote mentioned above to do so. Not sure it will solve your issues, really.
JTS tries to create new users in CCM if it thinks the user is not already there. This should not happen, because when this was introduced in 3.x you would have merged the user base in the upgrade. Another reason why this could happen is a wrong DB restore, where JTS is restored to a point in time before the state of the CCM DB, now tries to create a new user that it already created in RTC prior to the restore.
I am not sure what your situation is but I would suggest to get in contact with support anyway, in order to avoid trying to fix something with the wrong measures and ending up with more problems.
Thanks Ralph. We have some inconsistency with JTS and CCM user management. We have some missing users in CCM as compare to JTS. In other words, we have some users in JTS as active users but they are not visible in CCM. When we try to manually import them in CCM, we are getting error that user already exist. We have not restored DB from last 6 months or so.
We already have support PMR open for it but wanted to see if we get any resolution in the jazz forum.