Clément,
Thanks for the response.
A few follow up questions.
On the <referral> element, the valid options are:
* IGNORE
* THROUGH
* THROW
* ERROR
I'm assuming "IGNORE" means don't follow the referral, "THROUGH" means
follow the referral and process the results.
Is that correct?
What's the difference between THROW and ERROR? Does error just report
the problem in the log, while THROW actually generates an exception that
stops processing?
I read the section on aliases and I understand the basics, but I'm still
unsure of what the NEVER, SEARCH, FIND or ALWAYS actually do. Is there
somewhere that explains what each action actually does? The terms
"SEARCH" and "FIND" would seem to be synonymous and I'm not sure what
"ALWAYS" means. I'm guessing "NEVER" means references aren't followed at
all.
Lastly, I already read the <defaultPolicy> documentation. Really what
I'm looking for is clarification on what the verbs mean (i.e. FORCE,
KEEP, MERGE). I just want to make sure I document them correctly. I'm
guessing "FORCE" means the destination is always overwritten with the
source. "KEEP" might me don't overwrite the destination if the value
already exists. But I'm not really sure what "MERGE" would due (unless
it means it appends the source to the existing destination value).
Thanks again!
-Dan
On 11/4/2015 3:18 AM, Clément OUDOT wrote:
Le 03/11/2015 21:12, Dan G. Switzer, II a écrit :
I've read through the documentation and have done some searches, but
there are a couple of elements in the lsc.xml where the descriptions
in the documentation aren't helping me understand their purpose:
* lsc.xml
o <ldapConnection>
+ <referral> - One of the following values: IGNORE,
THROUGH, THROW or ERROR. Most of the time you should
either IGNORE them, go THROUGH or handle them as an ERROR
+ <derefAliases> - One of the following values: NEVER,
SEARCH, FIND or ALWAYS. Most of the time, use NEVER
o <propertiesBasedSyncOptions>
+ <defaultPolicy> - This is the value used to determine how
to synchronize attributes value in destination, according
to existing values, provided default, forced and create
values. It may take the following values: FORCE, KEEP or
MERGE
I suspect my lack of familiarity with LDAP might be part of the
problem (maybe these are well understood terms).
Could someone provide me with more details or better descriptions on
the above elements?
What exactly does the <referral> control? Why would you use it?
What exactly does the <derefAliases> control? Why would you use it?
What's a better definition for the <defaultPolicy> element? What are
the exact effects of each verb?
Hi Dan,
For referrals and aliases, you need to read docs about the LDAP
protocol. See for example
http://www.zytrax.com/books/ldap/ch7/referrals.html
For LSC policies, take a look at
http://lsc-project.org/wiki/documentation/latest/configuration/syncoptions?&#functionality_matrix
--
Clément OUDOT
Consultant en logiciels libres, Expert infrastructure et sécurité
Savoir-faire Linux
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
--
Dan G. Switzer, II
Giva, Inc.
Email: [email protected]
Web Site: http://www.givainc.com
See Our Customer Successes
http://www.givainc.com/customers-casestudies.htm
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
