Environment
Novell Vibe 3
Novell Vibe 4
Situation
You had eDir user imported into Vibe. By accident you deleted eDir user account but did not run LDAP sync yet, thus eDir / LDAP linked Vibe account still exist. When creating new eDir user account, it gets created with different GUID, thus by default you cannot match it with existing Vibe user. In Vibe you use GUID string for the "LDAP attribute that uniquely identifies a user or a group" parameter.
Resolution
Presuming you have created the same eDir user account at the same place as it was deleted from, you can modify Sitescape database and update existing "ldapGUID" attribute of existing Vibe user with newly created eDir user GUID value.
Use C1 or iManager to view a GUID string of newly created user in eDir.
Open a terminal window on Vibe server and connect to the Sitescape database. Here is example of command for MySQL database:
Enter password: ****
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 14
Server version: 5.5.32 MySQL Community Server (GPL)
Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> use sitescape;
Database changed
mysql> UPDATE SS_Principals SET ldapGuid='9bbd2de21fb07d4eac7ac0d4631eefa8' WHERE name='vibe4' and type='user';
Query OK, 1 row affected (0.02 sec)
Rows matched: 1 Changed: 1 Warnings: 0
mysql>
This is an example of user "vibe4" where we updated "ldapGUID" field by his new eDir GUID string.
Once this is done, you can run LDAP sync from Vibe adminconsole to verify that new eDir user matched existing Vibe user. When you do not see newly created eDir user being added to Vibe, then the match was successful.
Now you can login in the re-matched Vibe account with the "new user" eDir password.