Migrate internal Livelink user to LDAP user

Currently we have around 300 users in our Livelink system. The users are in the standard Livelink LDAP. We want to connect Livelink to active directory with directroy services. How can I migrate an livelink ldap user to a active directory user? The login name stays the same (only the password does not match). I need to keep the users permissions.

Find more posts tagged with

Comments

Chris_Wagg

Message from Chris Wagg <cwagg@opentext.com> via eLink

eLink

If you run a synch, and we find that new LDAP users are foundthat have the same username as existing users in Livelink, those users will beupdated to be synchronized users. As long as they are being authenticatedusing Directory Services (either LDAP or integrated windows auth) the change inpasswords won’t matter at all, as we don’t use the Livelink password toauthenticate them.

Obviously you will want to run a few test synchs to make surethat you have your filters right, but this should really be a prettystraightforward process.

---------------------------------------
Chris Wagg
Principal Product Specialist
Escalations Support Team
Open Text Corporation
Ph: 800-540-7292
---------------------------------------

From: eLink Discussion:Open Text Content Server Directory Services Discussion[mailto:directoryservices@elinkkc.opentext.com]
Sent: Thursday, July 29, 2010 9:49 AM
To: eLink Recipient
Subject: Migrate internal Livelink user to LDAP user

Migrate internal Livelink user to LDAP user

Posted by thalesnladmin (Oude Breuil, Tobi) on 2010/07/29 09:46

Currently we have around 300 users in our Livelink system. The users are in the standard Livelink LDAP.
We want to connect Livelink to active directory with directroy services.
How can I migrate an livelink ldap user to a active directory user? The login name stays the same (only the password does not match). I need to keep the users permissions.

[To reply to this thread, use your normal E-mail reply function.]
Discussion:	Open Text Content Server Directory Services Discussion
Livelink Server:	knowledge-wlweb01

To Unsubscribe from this Discussion, send an e-mail to unsubscribe.directoryservices@elinkkc.opentext.com.

Rainer_Meller_(livelink@zadi.de_--_(FIM_Delete))

Indeed setup an empty livelink system and setup ldap connection. If all parameters are right, you should get your ldap users synchronized to livelink. Also test if logon is working for ldap users and if all users are in the right groups. (Rule of the thump: all users / groups are migrated to "ldap-synchronized" that are matched. All other groups, useers remain "livelink-internal")Then backup the database and repository and import both to the empty livelink system, effectively cloning your productive environment. Now set log settings to excessive and check if all ldap users are updated and not created. If this goes right, backup productive livelink and install directory service module. Migrate the live system.Thinks to consider: You have to make sure that the logon for ldap users is working, on tomcat, which we use, we had to modify the server.xml to let tomcat do the authentication stuff. We did setup a 2nd entry lladmin to allow internal users to connect (mostly for debugging)If ldap is down no logon to livelink is possible (at least with tomcat)Carefully change, delete users and groups in ldap. It has direct impact on livelink on synchronization. At worst you have to reset permissions in livelink since the original groups are deleted and the new groups don't have permissions on the folders and documents. (This is because groups are always deleted if not found in ldap in contrast to users that can be set to disabled)I suggest you grant all users: logon, public access permissions. If you grant some users more permissions (after they are synchronized with ldap) directory services will not reset those permissions on each synchronization run.Good luck,Rainer Meller