A user has married. Their LDAP entry has been updated to reflect the new last name, the new email address, the new login name, and the new UID. Now, the user cannot log in to Connections anymore — neither with their old credentials nor with their new credentials.
Solution with Websphere Commandline Interface
Unless you are already aware that the problem has been caused by the TDI synchronization because of the change in UID, you first have to find out why exactly the user cannot log in anymore.
- Search the HCL Connections documentation for the steps to solve your problem.
- Start the wsadmin commandline interface as administrator. ATTENTION: All commands for the commandline interface are case sensitive!
- Activate the relevant Jython script.
- Perform the relevant Jython commands.
- Search the old user UID. Remember it.
- Search the new user UID. Remember it.
- Perform the UID swap command
Solution with Connections Administration Toolkit (CAT)
Navigate to User Management – By User. Then check the state of the affected user. In this case: User “Daisy Rest” has married, and her new name is “Daisy Duck”. Searching for the display name “Daisy” matches both “Daisy Rest” and “Daisy Duck”.
As you can see, only the user “Daisy Rest” is listed, and their state is inactive. The UID is still the old one. This means that the TDI synchronization failed. This happened because of the change in UID, which the TDI synchronization uses to match Connections Profiles users with the LDAP entries. To solve the problem, simply change the UID of the user by clicking “Change UID”.
Follow the instructions. A confirmation popup summarizes the changes and allows you to enter a comment. All changes, comments, and who made them, are logged by the CAT application. After the changes have been saved successfully, we give you helpful tips that come from our long-time experience.