[
https://issues.apache.org/jira/browse/SYNCOPE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346181#comment-15346181
]
ASF subversion and git services commented on SYNCOPE-876:
---------------------------------------------------------
Commit ddc2f3a18034b50ea84c0349f52570bc5885eaf3 in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=ddc2f3a ]
[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: 1.2.9, 2.0.0-M4
>
>
> 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)
