On 02/10/2018 17:22, Ben.H wrote:
Hi again,
Same situation. I have my external resource, and it is now populating the
external table. However, when I update the user, the connector does not get
updated. I'm not sure what triggers the update task on the connectors; I
was under the assumption that when an accounts details were updated any
connector that had a provision mapping for the account was triggered, but
that doesn't seem to be the case.
Hi,
the standard behavior is to generate propagation, upon User create,
update or delete - onto each resource assigned - directly or via group
membership - for which a USER mapping exists.
In case of update, only the resources where mapping contains attributes
affected by the update itself are considered for propagation.
What you are seeing now is the consequence of *not* having a mapping for
some attributes (as I suppose you are using a derivative of the sample
PropagationActions class I showed before): since no mapped attributes
are affected by update, no propagation is generated.
It's indeed possible to override the behavior above by subclassing [1] -
more specifically the update() method; once done, your new class must
also replace [1] in provisioning.properties.
HTH
Regards.
[1]
https://github.com/apache/syncope/blob/2_1_X/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/DefaultUserProvisioningManager.java
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
