You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/08/21 10:23:00 UTC

[jira] [Commented] (SYNCOPE-1575) Provide the ability to specify on which resources the user's status should be propagated

    [ https://issues.apache.org/jira/browse/SYNCOPE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181791#comment-17181791 ] 

ASF subversion and git services commented on SYNCOPE-1575:
----------------------------------------------------------

Commit fb621ec8846e6b6755afc771489ebae8c8ba4f67 in syncope's branch refs/heads/2_0_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=fb621ec ]

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