[ https://issues.apache.org/jira/browse/SYNCOPE-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17843395#comment-17843395 ]
ASF subversion and git services commented on SYNCOPE-1818: ---------------------------------------------------------- Commit 4f1f43f166b0f95008a860c613b629b5bd1538f5 in syncope's branch refs/heads/3_0_X from Andrea Patricelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=4f1f43f166 ] [SYNCOPE-1818] fixes wrong status propagation while pulling a status update (#703) --------- Co-authored-by: Francesco Chicchiriccò <ilgro...@apache.org> > Wrong status value propagated to external resources if changed while pulling > ---------------------------------------------------------------------------- > > Key: SYNCOPE-1818 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1818 > Project: Syncope > Issue Type: Bug > Components: core > Affects Versions: 3.0.6 > Reporter: Andrea Patricelli > Assignee: Andrea Patricelli > Priority: Major > Fix For: 3.0.7, 4.0.0 > > > In some specific cases the status of an user on an external resource could > change remotely. If, simultaneously, some other attribute is changed and a > propagation is fired the wrong status is propagated on the external resources. > For example, if an active (on syncope) user on resource-pull changes its > surname, email and status (set to disabled) and a pull is fired, a > propagation on some target resources occurs, depending on email and/or > surname mapping. Propagation status is wrong, for example if pulled > "disabled" the user is propagated active, i.e. {{__ENABLE__}} attribute is > set to {{false}}. -- This message was sent by Atlassian Jira (v8.20.10#820010)