[jira] [Resolved] (SYNCOPE-1818) Wrong status value propagated to external resources if changed while pulling
[ https://issues.apache.org/jira/browse/SYNCOPE-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-1818. Resolution: Resolved > 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)
[jira] [Commented] (SYNCOPE-1818) Wrong status value propagated to external resources if changed while pulling
[ https://issues.apache.org/jira/browse/SYNCOPE-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17843771#comment-17843771 ] ASF subversion and git services commented on SYNCOPE-1818: -- Commit 23f2e24906967955737b2ee0b3c72682d78cff14 in syncope's branch refs/heads/master from Andrea Patricelli [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=23f2e24906 ] [SYNCOPE-1818] fixes wrong status propagation while pulling a status update (#703) - Co-authored-by: Francesco Chicchiriccò > 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)