[
https://issues.apache.org/jira/browse/SYNCOPE-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17924513#comment-17924513
]
ASF subversion and git services commented on SYNCOPE-1864:
----------------------------------------------------------
Commit ec6ab7a3bec91a732d85f6b0efc626795d6e5e04 in syncope's branch
refs/heads/3_0_X from Marco Di Sabatino Di Diodoro
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=ec6ab7a3be ]
[SYNCOPE-1864] Fix test
> Unwanted password propagation after update on pull
> --------------------------------------------------
>
> Key: SYNCOPE-1864
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1864
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.10, 4.0.0-M0
> Reporter: Marco Di Sabatino Di Diodoro
> Assignee: Marco Di Sabatino Di Diodoro
> Priority: Major
> Fix For: 3.0.11, 4.0.0
>
>
> During a pull task in update, if a new resource is assigned to the user with
> a password patch only for that resource, Syncope propagates the password to
> all resources associated to that user.
> To reproduce the issue:
> # Create a user with two resources
> # Create a pull task that updates the user by assigning a new resource with
> a password only for that resource
> # Run the pull task
> In all propagation tasks the password attribute is present.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
