Repository: syncope Updated Branches: refs/heads/2_0_X 50e6aece7 -> 1738f69f7 refs/heads/master a482f0bae -> b667bb811
http://git-wip-us.apache.org/repos/asf/syncope/blob/1a3a05e2/src/main/asciidoc/reference-guide/concepts/externalresources.adoc ---------------------------------------------------------------------- diff --git a/src/main/asciidoc/reference-guide/concepts/externalresources.adoc b/src/main/asciidoc/reference-guide/concepts/externalresources.adoc index 754959e..1cd54ed 100644 --- a/src/main/asciidoc/reference-guide/concepts/externalresources.adoc +++ b/src/main/asciidoc/reference-guide/concepts/externalresources.adoc @@ -155,6 +155,8 @@ Besides the items documented above, some more data needs to be specified for a c http://connid.tirasa.net/apidocs/1.4/org/identityconnectors/framework/common/objects/ObjectClass.html[object class^] shall be used during communication with the Identity Store; predefined are `\\__ACCOUNT__` for Users and `\\__GROUP__` for Groups +* whether matches between user / group / any object's attribute values and their counterparts on the Identity Store +should be performed in a case-sensitive fashion or not * Object link - only required by some connector bundles as https://connid.atlassian.net/wiki/display/BASE/LDAP[LDAP^] and https://connid.atlassian.net/wiki/pages/viewpage.action?pageId=360482[Active Directory^], generally specifies the model http://git-wip-us.apache.org/repos/asf/syncope/blob/1a3a05e2/src/main/asciidoc/reference-guide/concepts/provisioning/pull.adoc ---------------------------------------------------------------------- diff --git a/src/main/asciidoc/reference-guide/concepts/provisioning/pull.adoc b/src/main/asciidoc/reference-guide/concepts/provisioning/pull.adoc index b37f34d..2d88bf4 100644 --- a/src/main/asciidoc/reference-guide/concepts/provisioning/pull.adoc +++ b/src/main/asciidoc/reference-guide/concepts/provisioning/pull.adoc @@ -25,8 +25,8 @@ Pull is the mechanism used to acquire identity data from Identity Stores; for ea Pull task execution involves querying the external resource and then processing each entity in an isolated transaction; a retrieved entity can be: -. _matching_ if a corresponding internal entity was found, according to the <<policies-pull,pull policy>> set for the -enclosing external resource; +. _matching_ if a corresponding internal entity was found, according to the <<mapping,mapping>> of - or the +<<policies-pull,pull policy>> set for, if present - the enclosing external resource; . _unmatching_ otherwise. Once this has been assessed, entities are processed according to the matching / unmatching rules specified for the pull task:
