[jira] [Resolved] (SYNCOPE-601) AD deleted object synchronization fails if a sync policy is specified on one or more attributes that can have no values on Syncope

["Marco Di Sabatino Di Diodoro (JIRA)" <ji...@apache.org>]

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

Marco Di Sabatino Di Diodoro resolved SYNCOPE-601.
--------------------------------------------------
    Resolution: Fixed

> AD deleted object synchronization fails if a sync policy is specified on one or more attributes that can have no values on Syncope
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SYNCOPE-601
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-601
>             Project: Syncope
>          Issue Type: Bug
>    Affects Versions: 1.1.8, 1.2.0
>            Reporter: fabio martelli
>            Assignee: Marco Di Sabatino Di Diodoro
>             Fix For: 1.1.9, 1.2.1, 1.3.0
>
>
> During AD synchronization (via ConnID AD - JNDI - connector bundle) returned connector objects about deleted objects don't have any profile attribute specified (see https://connid.atlassian.net/browse/AD-36).
> If a sync posicy is specified to perform a correlation among one or more internal profile attributes, the first user with no values about that attribute will match this correlation rule and maybe removed.
> The query has to be changed in order to avoid this behavior (for delteted object and creted-updated):
> 1. if one or more connector object attributes related to the correlation rule don't exist avoid the query execution ... no match
> 2. if all the connector object attributes related to the correlation rule exist then perform the query as is



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