syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SYNCOPE-876) Fake after object reported by propagation in case of delete
Date Thu, 23 Jun 2016 09:24:16 GMT

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

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

Commit 326397bb58df67216928c59ed14c5a7474422e25 in syncope's branch refs/heads/1_2_X from
[~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=326397b ]

[SYNCOPE-876] Fix provided


> Fake after object reported by propagation in case of delete
> -----------------------------------------------------------
>
>                 Key: SYNCOPE-876
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-876
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.2.8, 2.0.0-M3
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> SYNCOPE-858 improved the way how Syncope handles the connector object returned after
create / update, especially when the external resource is responsible for generating the {{__UID__}}
value.
> Unfortunately, this currently leads to the generation of fake connector objects in case
of delete, where such object is instead expected to be null.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message