[
https://issues.apache.org/jira/browse/SYNCOPE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181792#comment-17181792
]
ASF subversion and git services commented on SYNCOPE-1575:
----------------------------------------------------------
Commit 75d206485b57795d9dbf08f82a5523a9b70a4ac0 in syncope's branch
refs/heads/2_1_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=75d2064 ]
[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)
