[jira] [Resolved] (SYNCOPE-397) Double update propagation with virtual attributes on already associated resource when changing password and adding new resource

["fabio martelli (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SYNCOPE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

fabio martelli resolved SYNCOPE-397.
------------------------------------

    Resolution: Fixed

Thank you again Andrea for your contribution.
                
> Double update propagation with virtual attributes on already associated resource when changing password and adding new resource
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SYNCOPE-397
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-397
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.1.2
>            Reporter: Andrea Patricelli
>             Fix For: 1.1.3, 1.2.0
>
>         Attachments: SYNCOPE-397.patch
>
>
> steps (run Syncope with -Pdev profile):
> 1. modify resource-csv mapping external attribute mail with virtual attribute virtualdata (assign BOTH
>     purpose to the attribute, it may also work with SYNCHRONIZATION).
> 2. create a new user with all required (for csv) fields set to value (username, surname, mail, type, ecc), in
>     particular add derived attributes csvuserid and cn and virtual attribute virtualdata
> 3. add to user resource-csv as resource, save and open it in edit mode.
> 4. add new resource to user, ws-target-resource-2, edit virtual attribute virtualdata.
> 5. edit password and check the checkbox to change password also on Syncope (don't check all resouces, csv must not be checked), checkbox for ws-target-resource-2 is already set. Save user
> It will be noticed a double propagation of user on both resources due to method fillVirtual() in PropagationManager.java

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira