nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Change synchronisation from NTLM to LDAP.

Paul Langham

We have users who are not happy with the current NTLM synchronisation and the limitations with first name and last name eg(first name Te Atarangi last name Smith) and under the current setup the last name is Atarangi Smith), I am investigating switching to LDap to allow livelink to read first names and second names more effectively just wanting to know the implications of changing it and if you have any ideas or documentation on doing so other than the Directory services standard documentation, we are using a windows environment (Server 2003 and IIS6) running livelink 9.7 and directory services 2.3.4any assistance would be appreciated

Find more posts tagged with

Comments

Chris_Wagg

Message from Chris Wagg via eLinkPaul,The following two KB articles give a lot of information aboutsynchronizations. One of them gives an in depth description of how toset up an LDAP read only synch:https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=4028432&objAction=ArticleView&viewType=1andhttps://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=4432890&objAction=ArticleView&viewType=1Moving to an LDAP or LDAP read only synch is a good move. These synchsoffer some real advantages over NTLM. The thing to be careful of is,make sure you have it right before you run the synch in production. Ifit is wrong, you could end up deleting or disabling all of your users.So my recommendation would be to set up a test environment that you canmigrate from NTLM to LDAP, and be sure you have a valid backup beforerunning the synch in production for the first time. ---------------------------------------Chris WaggPrincipal Product SpecialistEscalations Support TeamOpen Text CorporationPh: 800-540-7292--------------------------------------------Original Message-----From: eLink Discussion: Livelink Directory Services Discussion[mailto:directoryservices@elinkkc.opentext.com] Sent: Thursday, July 31, 2008 8:36 PMTo: eLink RecipientSubject: Change synchronisation from NTLM to LDAP.Change synchronisation from NTLM to LDAP.Posted by Langham, Paul on 07/31/2008 08:30 PMWe have users who are not happy with the current NTLM synchronisationand the limitations with first name and last name eg(first name TeAtarangi last name Smith) and under the current setup the last name isAtarangi Smith), I am investigating switching to LDap to allow livelinkto read first names and second names more effectively just wanting toknow the implications of changing it and if you have any ideas ordocumentation on doing so other than the Directory services standarddocumentation, we are using a windows environment (Server 2003 and IIS6)running livelink 9.7 and directory services 2.3.4any assistance would be appreciated[To reply to this thread, use your normal E-mail reply function.]============================================================Discussion: Livelink Directory Services Discussionhttps://knowledge.opentext.com/knowledge/llisapi.dll/open/3062146Livelink Server:https://knowledge.opentext.com/knowledge/llisapi.dllTo Unsubscribe from this Discussion, send an e-mail tounsubscribe.directoryservices@elinkkc.opentext.com.

Paul Langham

i will let you know how i get on, cheers

Chris_Cavanaugh

We're going to attempt the same change over, I'm going over the documentation now. One question, for the accounts I have in livelink already, if the username matches that in AD, will they match and synchronize? Or am I really losing the old accounts and creating new? Thanks for any guidance someone can provide.

Appu_Nair

Perhaps Chris Wagg will see this in time.I would make a test environment and test this thory,although I don't think it is based on a string comparison 'nairkn' a userid in AD may have a SID .If AD now allotts a new "nairkn" it will have a new SID.The Ad syncronization is probably going to create a new login "nairkn" in this scenario because the old user and the new user is the same by name but not the same person.it can't if the old "naikn" is not deleted/disabled.If SID's match then it make use of userdata assoc field in KUAF.I don't know too much about this process but was just sharing thinking it may help.

Chris_Wagg

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

eLink

If the usernames match up it will just update the users, not create all new ones.

Obviously, if you can do this in a test environment first, that will help identify any issues before you go into production.
Sent From My Blackberry
---------------------------------------
Chris Wagg
Principal Product Specialist
Escalations Support Team
Open Text Corporation
Ph: 800-540-7292
---------------------------------------

From: eLink Discussion: Livelink Directory Services Discussion <directoryservices@elinkkc.opentext.com>
To: eLink Recipient <devnull@elinkkc.opentext.com>
Sent: Fri Feb 27 17:09:16 2009
Subject: Change synchronisation from NTLM to LDAP.

Change synchronisation from NTLM to LDAP.		Posted by christian.cavanaugh@gdit.com (Cavanaugh, Chris ) on 2009/02/27 17:04
In reply to: Thanks for input		Posted by tepuni01admin (Langham, Paul) on 2008/08/06 00:18

Chris_Wagg

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

eLink

But inthis case it is the same I D. In this case it would be a string comparisson as NTLM synch would not get the UniqueID that an LDAP synch would.

However, DS could update way too many users to just assume you have everything set up correctly, which is why I highly recomment testing first.
Sent From My Blackberry
---------------------------------------
Chris Wagg
Principal Product Specialist
Escalations Support Team
Open Text Corporation
Ph: 800-540-7292
---------------------------------------

From: eLink Discussion: Livelink Directory Services Discussion <directoryservices@elinkkc.opentext.com>
To: eLink Recipient <devnull@elinkkc.opentext.com>
Sent: Fri Feb 27 17:29:54 2009
Subject: Perhaps Chris Wagg will see this in time.I would make a test environment and...

Perhaps Chris Wagg will see this in time.I would make a test environment and...		Posted by anair@alitek.com (Nair, Appu) on 2009/02/27 17:28
In reply to: Change synchronisation from NTLM to LDAP.		Posted by christian.cavanaugh@gdit.com (Cavanaugh, Chris ) on 2009/02/27 17:04