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/29 17:44:36 UTC

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=14297114#comment-14297114 ] 

Francesco Chicchiriccò edited comment on SYNCOPE-632 at 1/29/15 4:44 PM:
-------------------------------------------------------------------------

Once I have added a specific integration test (see [RoleTestITCase#issueSYNCOPE632|https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blobdiff;f=core/src/test/java/org/apache/syncope/core/rest/RoleTestITCase.java;h=6e384d4ea5535af1dab500bcdcbc41fe0dce8f02;hp=a6a6009e7946a42b7fb721d642e5d00f11c3a735;hb=3237d26;hpb=60a62434e16a3a811d8f549e2d4351633667e90c]) I realized that this issue was a bit more cumbersome than expected, so I had to re-work the provided patch to adapt it to the general use case; anyway, now everything should be working.


was (Author: ilgrosso):
Once I have added a specific integration test (see RoleTestITCase#issueSYNCOPE632) I realized that this issue was a bit more cumbersome than expected, so I had to re-work the provided patch to adapt it to the general use case; anyway, now everything should be working.

> 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)