You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2015/01/28 11:57:35 UTC
[jira] [Updated] (SYNCOPE-632) Errors during update propagation
when derived attribute is configured as account id
[ https://issues.apache.org/jira/browse/SYNCOPE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò updated SYNCOPE-632:
-------------------------------------------
Description:
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).
Here you can find a patch create with Francesco's collaboration:
https://paste.apache.org/2zJK
Relevant e-mail thread: http://markmail.org/message/dlrtnh7phzechdy4
was:
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).
Here you can find a patch create with Francesco's collaboration:
https://paste.apache.org/2zJK
Affects Version/s: 1.2.1
Fix Version/s: (was: 1.2.1)
1.3.0
1.2.2
Assignee: Francesco Chicchiriccò
Summary: Errors during update propagation when derived attribute is configured as account id (was: UserDataBinder and RoleDataBinder not retrieve correct account ids for external resource propagation)
> Errors during update propagation when derived attribute is configured as account id
> -----------------------------------------------------------------------------------
>
> Key: SYNCOPE-632
> URL: https://issues.apache.org/jira/browse/SYNCOPE-632
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 1.2.1
> Reporter: Nicola Baiocco
> Assignee: Francesco Chicchiriccò
> Fix For: 1.2.2, 1.3.0
>
>
> 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).
> Here you can find a patch create with Francesco's collaboration:
> https://paste.apache.org/2zJK
> Relevant e-mail thread: http://markmail.org/message/dlrtnh7phzechdy4
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)