Uploaded image for project: 'Syncope'
  1. Syncope
  2. 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

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.1.8, 1.2.0
    • 1.1.9, 1.2.1, 2.0.0-M1
    • None
    • None

    Description

      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

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mdisabatino Marco Di Sabatino Di Diodoro
            fmartelli Fabio Martelli
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment