On 27/01/2015 13:29, Francesco Chicchiriccò wrote:
On 26/01/2015 16:25, Nicola Baiocco wrote:
Hi,
we have some problem during update propagations to external resource
of users and roles in Syncope 1.2.1.
In our case, the external resource has a derived attribute configured
as account id.
During the propagation task it seems that syncope performs a
getRemoteObject operation (in AbstractPropagationTaskExecutor)
passing username/rolename attribute instead of the designed account
id attribute (internal attribute specified in user/role mapping
configuration).
This behavior it seems an issue and we have resolved with attached
patch.
Could you confirm that?
Otherwise if we have a misunderstanding could you explain what is the
business logic behind this routine (UserDataBinder update and
RoleDataBinder update).
Hi Nicola,
sorry I cannot see your patch - probably it's safer to paste it to
https://paste.apache.org/
Sorry, http://apaste.info/ should work (the one above is for ASF
committers).
You should also provide some more information about your resource
mapping.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/
