Home
Extended ECM
API, SDK, REST and Web Services
LDAP synchronization with Active Directory
Dale_Baldwin
We've just installed the Livelink 9.5 SP1 product on Solaris 8 and would like to run the LDAP synchronization process. We have run into the issue with the limitation of 1000 users on a non-Windows platform. We need to synchronize 4000+ users and wondered if anyone has come up with a workaround in Livelink (we cannot change any of the Active Directory settings to make this work) to be able to synchronize more thant 1000 users. Is is possible to run multiple synchronization processes??
Find more posts tagged with
Comments
Sanjay_Kabra_(skabra_-_(deleted))
Hi Chris,We have a similar sceanrio where we have to syncronize 1500+ users. Did u get any way out to achieve 4000+ users synchronization? If yes then let us know the way.Thanks
Daniel_Connolly_(danielconnolly_-_(deleted))
1000 user limit? We run on Windows, but the idea that there might be that limit in any OS is a bit strange.Are you sure you don't mean the 1000 users per group limit? We have come across that limit, which also affects the DefaultGroup. So, with LDAP, you effectively *have* to use Departmental mapping if you have more than 1000 users, otherwise they are all put in the DefaultGroup which hits the limit.
Jacques_Laforest
if this is the problem you can also change the value in the .iniwe have 50.000+ users in the default group
Mahesh_Pinnamaneni
does all 50000+ users in the same group in AD?Even we are facing some problems with AD sync, LL wil return 0 users if there are more than 1000 users in a particular group. we had confirmed from AD people that there is no such restriction appied on AD to query only 1000 users.any solved this probs?Thanks & Regards,Mahesh P
Chris_Wagg
the problem here is not due to a limitation in Active Directory, it has to do with the way that AD returns LDAP search results. AD uses paging to return its results, sending the results in 1000 object chunks. The Unix version of the LDAP dropin is not able to deal with these paged results. Thus, if you are returning more than 1000 objects, the synch will fail.This is one of the primary reason why Opentext does not support synchronizing a Unix Livelink with Active Directory.i am aware of a few customers who have set up an environment to get around this. They replicate their AD data to a Sun One or other Directory Server. I hope this helps.Chris Wagg
Mahesh_Pinnamaneni
Our Livelink & AD were both on windows platform.Also I have checked with AD team that there was no such restriction imposed.is there any patch which wil solve this?thanks & regards,Mahesh P
Chris_Wagg
Message from Chris Wagg via eLinkMahesh,My response was specifically to Dale's original question. If you areexperiencing this problem and all of your systems are on Windows, then Iwould recommend opening a ticket for your issue, as the cause is not theone I outlined in my previous email.---------------------------------------Chris WaggSenior Product SpecialistOpen Text CorporationPh: 800-540-7292Email: cwagg@opentext.com--------------------------------------------Original Message-----From: eLink Discussion: Livelink Directory Services Discussion[mailto:directoryservices@elinkkc.opentext.com] Sent: Thursday, November 23, 2006 8:37 AMTo: eLink RecipientSubject: Our Livelink & AD were both on windows platform.Our Livelink & AD were both on windows platform.Posted by Pinnamaneni, Mahesh on 11/23/2006 08:36 AMOur Livelink & AD were both on windows platform.Also I have checked with AD team that there was no such restrictionimposed.is there any patch which wil solve this?thanks & regards,Mahesh P[To reply to this thread, use your normal E-mail reply function.]============================================================Topic: LDAP synchronization with Active Directory
https://knowledge.opentext.com/knowledge/llisapi.dll/open/4229650Discussion
: Livelink Directory Services Discussion
https://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.