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

Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (Jira)" <ji...@apache.org> on 2019/09/10 12:35:00 UTC

[jira] [Resolved] (SYNCOPE-1493) Mapping unique schema as remote key never matches internal objects

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

Francesco Chicchiriccò resolved SYNCOPE-1493.
---------------------------------------------
    Resolution: Fixed

> Mapping unique schema as remote key never matches internal objects
> ------------------------------------------------------------------
>
>                 Key: SYNCOPE-1493
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1493
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.13, 2.1.4
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 2.0.14, 2.1.5, 3.0.0
>
>
> When unique schema is used as remote key for mapping an External Resource, any given Pull Task execution will result into an attempt to create (never updated) an internal object.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)