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; } } }

Differentiating internal users from external usrs

Belinda_Mays

1) When we set the synch parameter to disable, delete, ect. Does that only impact internal users or will the external users get disabled when synch runs because they are not in the AD?2) How does the synchronization process differentiate between internal users that need to be synched and external users that do not need to be synched?3) Can synched users be placed in Content Server department groups based on anything other than an AD attribute field? For example can we setup a filter to synch all the users in the abcr Active Directory group and have them all placed in the abcd Content Server department even though abcd is not an attribute in the user records.

Find more posts tagged with

Comments

Kevin_Bailey

Message from Kevin Bailey <kbailey@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

#1 it will only delete/disable users that were synched to that specific sync source

#2 Livelink keeps a table that indicates users that were synched, and their synch source

#3 Not sure, you can set up a department mapping so that all the users would be placed in abcd group (instead of DefaultGroup)

From: eLink Discussion: Open Text Directory Services Discussion [mailto:directoryservices@elinkkc.opentext.com]
Sent: Thursday, February 18, 2010 11:15 AM
To: eLink Recipient
Subject: Differentiating internal users from external usrs

Differentiating internal users from external usrs

Posted by bmays (Mays, Belinda) on 2010/02/18 11:14

1) When we set the synch parameter to disable, delete, ect. Does that only impact internal users or will the external users get disabled when synch runs because they are not in the AD?

2) How does the synchronization process differentiate between internal users that need to be synched and external users that do not need to be synched?

3) Can synched users be placed in Content Server department groups based on anything other than an AD attribute field? For example can we setup a filter to synch all the users in the abcr Active Directory group and have them all placed in the abcd Content Server department even though abcd is not an attribute in the user records.

Appu_Nair

On #3 instead of the department mapping what we have practiced is a tweak in the table.The DepartmentMapping table and LLDS_USERDATA are linked by CONFIGIDWe go to it and change it in departmentmappingDSConfig_001 Default MYDEPARTMENTNote livelink Out of the Box will put every user into Default Group unless you tweak this.The tweak is needed because the GUI will not allow it to be changed

Kevin_Bailey

Message from Kevin Bailey <kbailey@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

maybe I am misunderstanding you. You can change the default mapping via the GUI:

And make sure that you have enabled department mapping on the edit synch source parameters:

From: eLink Discussion: Open Text Directory Services Discussion [mailto:directoryservices@elinkkc.opentext.com]
Sent: Thursday, February 18, 2010 12:43 PM
To: eLink Recipient
Subject: On #3 instead of the department mapping what we have practiced is a tweak in...

On #3 instead of the department mapping what we have practiced is a tweak in...		Posted by anair@alitek.com (Nair, Appu) on 2010/02/18 12:41
In reply to: RE Differentiating internal users from external usrs		Posted by kbailey (Bailey, Kevin) on 2010/02/18 12:06

On #3 instead of the department mapping what we have practiced is a tweak in the table.The DepartmentMapping table and LLDS_USERDATA are linked by CONFIGID
We go to it and change it in departmentmapping
DSConfig_001@ @ Default@ @ MYDEPARTMENT
Note livelink Out of the Box will put every user into Default Group unless you tweak this.The tweak is needed because the GUI will not allow it to be changed

Appu_Nair

Hi Kevin,Can you see whet I should be doing to get around this error.I do not understand LDAP that very well.The Tweak is done so that we can get all the users in the user search filter to a different group other than 'Default Group'

Chris_Wagg

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

eLink

I believe this issue is fixed in a newer version of DirectoryServices, however you can work around this by changing it in the database. Thereis a table called DepartmentMappings, it has only 2 columns and is used onlyfor these mappings, so modifying it is relatively safe.

You don’t actually need to enable department mapping for this towork, though, the default department mapping will be used any time a user can’tbe mapped to a department.

A word of caution, putting all of your users into one departmentis the same as putting them all into one group, you will see a performance impactif you have too many users in one group. By default we only allow 1000.

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

From: eLink Discussion:Open Text Directory Services Discussion[mailto:directoryservices@elinkkc.opentext.com]
Sent: Thursday, February 18, 2010 2:27 PM
To: eLink Recipient
Subject: Hi Kevin,

Hi Kevin,		Posted by anair@alitek.com (Nair, Appu) on 2010/02/18 14:24
In reply to: RE On #3 instead of the department mapping what we have practiced is a tweak in...		Posted by kbailey (Bailey, Kevin) on 2010/02/18 12:53

Hi Kevin,
Can you see whet I should be doing to get around this error.I
do not understand LDAP that very well.

The Tweak is done so that we can get all the users in the user search filter to a different group other than 'Default Group'

Attachment Links:

Why Tweak is needed.docx (62 KB)

[To reply to this thread, use your normal E-mail reply function.]
Topic:	Differentiating internal users from external usrs
Discussion:	Open Text Directory Services Discussion
Livelink Server:	knowledge-wlweb01

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

Kevin_Bailey

Message from Kevin Bailey <kbailey@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

what version of directory services are you running?

From: eLink Discussion: Open Text Directory Services Discussion [mailto:directoryservices@elinkkc.opentext.com]
Sent: Thursday, February 18, 2010 2:27 PM
To: eLink Recipient
Subject: Hi Kevin,

Hi Kevin,		Posted by anair@alitek.com (Nair, Appu) on 2010/02/18 14:24
In reply to: RE On #3 instead of the department mapping what we have practiced is a tweak in...		Posted by kbailey (Bailey, Kevin) on 2010/02/18 12:53

Hi Kevin,
Can you see whet I should be doing to get around this error.I
do not understand LDAP that very well.

The Tweak is done so that we can get all the users in the user search filter to a different group other than 'Default Group'

Kevin_Bailey

Message from Kevin Bailey <kbailey@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

that was what I was looking at: the version of Directory Services he is running. I do recall a code issue in the past and it is fixed in the current version (3.1.0)

From: eLink Discussion: Open Text Directory Services Discussion [mailto:directoryservices@elinkkc.opentext.com]
Sent: Thursday, February 18, 2010 2:37 PM
To: eLink Recipient
Subject: RE Hi Kevin,

RE Hi Kevin,		Posted by cwagg (Wagg, Chris) on 2010/02/18 14:36
In reply to: Hi Kevin,		Posted by anair@alitek.com (Nair, Appu) on 2010/02/18 14:24

Message from Chris Wagg <cwagg@opentext.com> via eLink I believe this issue is fixed in a newer version of Directory Services, however you can work around this by changing it in the database. There is a table called DepartmentMappings, it has only 2 columns and is used only for these mappings, so modifying it is relatively safe. You don’t actually need to enable department mapping for this to work, though, the default department mapping will be used any time a user can’t be mapped to a department. A word of caution, putting all of your users into one department is the same as putting them all into one group, you will see a performance impact if you have too many users in one group. By default we only allow 1000. --------------------------------------- Chris Wagg Principal Product Specialist Escalations Support Team Open Text Corporation Ph: 800-540-7292 --------------------------------------- From: eLink Discussion: Open Text Directory Services Discussion [mailto:directoryservices@elinkkc.opentext.com] Sent: Thursday, February 18, 2010 2:27 PM To: eLink Recipient Subject: Hi Kevin, Hi Kevin,		Posted by anair@alitek.com (Nair, Appu) on 2010/02/18 14:24
In reply to: RE On #3 instead of the department mapping what we have practiced is a tweak in...		Posted by kbailey (Bailey, Kevin) on 2010/02/18 12:53

Hi Kevin,
Can you see whet I should be doing to get around this error.I
do not understand LDAP that very well.

The Tweak is done so that we can get all the users in the user search filter to a different group other than 'Default Group'

Attachment Links:

Why Tweak is needed.docx (62 KB)

[To reply to this thread, use your normal E-mail reply function.]
Topic:	Differentiating internal users from external usrs
Discussion:	Open Text Directory Services Discussion
Livelink Server:	knowledge-wlweb01

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

Appu_Nair

Message from Appu Nair <anair@alitek.com> via eLink

eLink

I see form ChrisWagg’s posting that in DirSvcs 3.1.0 this is fixed.The fact is that Iinstalled this form the ELS10.1.0 bundle so did not think to upgrade this onemodule.Maybe that is the better way.

The reason fornot using ‘Default Group’ is what they teach you at livelink 101class.the Default Group is a catch all bucket that is better not used in ACL’s.Hencewe tend not to synchronize livelink users into the

Default Groupand for some time this was the way it used to be done.

Thanks Gentsfor your time

From: eLink Discussion:Open Text Directory Services Discussion[mailto:directoryservices@elinkkc.opentext.com]
Sent: Thursday, February 18, 2010 1:42 PM
To: eLink Recipient
Subject: RE Hi Kevin, 2

RE Hi Kevin, 2		Posted by kbailey (Bailey, Kevin) on 2010/02/18 14:42
In reply to: Hi Kevin,		Posted by anair@alitek.com (Nair, Appu) on 2010/02/18 14:24

Message from Kevin Bailey <kbailey@opentext.com> via eLink

what version of directory services are you running?

From: eLink Discussion: Open Text Directory Services Discussion [mailto:directoryservices@elinkkc.opentext.com]
Sent: Thursday, February 18, 2010 2:27 PM
To: eLink Recipient
Subject: Hi Kevin,

Hi Kevin,		Posted by anair@alitek.com (Nair, Appu) on 2010/02/18 14:24
In reply to: RE On #3 instead of the department mapping what we have practiced is a tweak in...		Posted by kbailey (Bailey, Kevin) on 2010/02/18 12:53

Hi Kevin,
Can you see whet I should be doing to get around this error.I
do not understand LDAP that very well.

The Tweak is done so that we can get all the users in the user search filter to a different group other than 'Default Group'

[To reply to this thread, use your normal E-mail reply function.]
Topic:	Differentiating internal users from external usrs
Discussion:	Open Text Directory Services Discussion
Livelink Server:	knowledge-wlweb01

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

Belinda_Mays

So with DS 3.1.0 is it possible to have several AD groups map to several different Content Server groups during one or multiple synchs? If so how? Could the department mapping handle a scenario like the one below even if the AD Group is not an attribute in the directory?AD Group - Content Server Default Groupa -> ab -> bc -> cd -> d