On 11/11/2012 21:21, ernst Developer wrote: > Hi, > > I was wondering about the behavior of a setup in Syncope with 1 > connector having 2 resources (SYNCResource and UPDATEResource). > > SYNCResource : this resources is meant for handling the synchronization. > UPDATEResource: this resource is meant for updating. Only a limited > set of schema fields (subset of the configured mappings in the > SYNCResource) is configured. > > When updating the user in Syncope, the propagation should only execute > on the UPDATEResource, not on the SYNCResource. Is this possible by > configuration in Syncope?
Sure: by default SYNCed users are not assigned any role or resource: this means that by default no propagation occurs at all after synchronization. You can, however, modify this behavior by editing the user template associated with the synchronization task you are running: in this way you can associate any role and/or resource (and customize any attribute, BTW). > What happens with the update in the corresponding connected system? > For the SYNCResource this is an update in its connector, and the sync > results in another update (the same) of the Syncope user, including > all the corresponding propagations. One of them is of course the > propagation by the UPDATEResource, and the party starts all over again. In order to prevent circular endless updates, the immediate propagation on the same syncing resource is disabled: this means that when you are synchronizing from Active Directory and assigning a DB resource and the same Active Directory resource to synchronized users (via user template), the actual propagation will only happen towards the DB resource. > Is what I describe above the actual behavior, or am I missing something? I hope this clarifies a bit. Regards. -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/
