You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Andrea Patricelli (JIRA)" <ji...@apache.org> on 2018/07/24 12:50:00 UTC
[jira] [Assigned] (SYNCOPE-1343) Attributes are not reset after
pull of null values
[ https://issues.apache.org/jira/browse/SYNCOPE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrea Patricelli reassigned SYNCOPE-1343:
------------------------------------------
Assignee: Andrea Patricelli
> Attributes are not reset after pull of null values
> --------------------------------------------------
>
> Key: SYNCOPE-1343
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1343
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 2.0.9, 2.1.0
> Reporter: Andrea Patricelli
> Assignee: Andrea Patricelli
> Priority: Major
> Fix For: 2.0.10, 2.1.1, 3.0.0
>
>
> Define a connector for some kind of persistence unit (LDAP, SQL, does not matter) and an associated resource.
> Create a set of provisioning rules for that resource, especially define a mapping with an attribute that is nullable on the resource and Syncope.
> Create a pull task on that resource and enable create and update (set also matching and unmatching rules accordingly).
> Pull objects from the resource in order to create them on Syncope, then try to reset values on the external resource for some mapped attribute and re-pull in order to update obejcts. You'll see that the values are *not* reset on Syncope.
>
> an test case is explained is [here|http://syncope-user.1051894.n5.nabble.com/Null-External-fields-are-not-updating-in-syncope-during-PULL-task-td5709936.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)