How to Configure Identity Synchronization for Windows (ISW) if Several Synchronization User Lists Have the Same Base DN and Filter (Doc ID 1389482.1)

Last updated on DECEMBER 08, 2016

Applies to:

Oracle Directory Server Enterprise Edition - Version 5.2 to 11.1.1.5.0 [Release 5.0 to 11gR1]
Information in this document applies to any platform.

Symptoms

In this example we  want to synchronize one branch of Directory Server

E.g.

ou=people,dc=example,dc=com



Two branches in Active Directory   ( windows 7 users and the others )


ou=win7users,dc=isw-windom,dc=fr,dc=oracle,dc=com
cn=users,dc=isw-windom,dc=fr,dc=oracle,dc=com



There are no specific attribute to make the difference on the two branches on AD
and in Documentation ISW Deployment Guide this specific case has been covered.

http://docs.oracle.com/cd/E20295_01/html/820-0386/aaqay.html#gdpdl

Extract from the documentation:

 

Note:
  If there is no SUL filter or it has only a single component, an SUL
filter (or filter component) is added. This SUL filter component is different for each SUL but always evaluates to true.

  For example, the SUL definitions for SUL_AD_WEST and SUL_AD_EAST could also
  be defined as follows:
 
(&(!(uid=c-*)(destinationindicator=eb.com) (!(bogusAttr=SUL_AD_WEST)))
      (&(!(uid=c-*)(destinationindicator=eb.com) (!(bogusAttr=SUL_AD_EAST)))



If you try this feature you will see is not possible to save your configuration
and you will have a similar error message as below.


[Error] The Filter, '(&(cn=*)(bogusAttr=win7))', is not valid.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms