[ https://issues.apache.org/jira/browse/SYNCOPE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181793#comment-17181793 ]
ASF subversion and git services commented on SYNCOPE-1575: ---------------------------------------------------------- Commit 44d678579e6ee50cbc4f937bb8773af089e81dc0 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=44d6785 ] [SYNCOPE-1575] For suspend / reactivate, pass PropagationByResource instance from workflow execution back to ProvisioningManager > Provide the ability to specify on which resources the user's status should be > propagated > ---------------------------------------------------------------------------------------- > > Key: SYNCOPE-1575 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1575 > Project: Syncope > Issue Type: Improvement > Components: core > Affects Versions: 2.0.15, 2.1.6 > Reporter: Marco Di Sabatino Di Diodoro > Assignee: Francesco Chicchiriccò > Priority: Major > Fix For: 2.0.16, 2.1.7, 3.0.0 > > > If only the state changes during a pull from a resource, Syncope doesn't > propagate the change. It's necessary to improve the management of this use > case by allowing to specify through the worklow tasks on which resources the > state must be propagated. -- This message was sent by Atlassian Jira (v8.3.4#803005)