Creation of Child OU with OID Connector Fails with "LDAP: error code 32 - Parent entry not found in the directory"
Last updated on OCTOBER 10, 2016
Applies to:Identity Manager Connector - Version 188.8.131.52 and later
Information in this document applies to any platform.
**Checked For Relevance on 02-Aug-2013**
After modifying the Lookup.OID.Configuration from the ldapOrgUnitObjectClass to orclContainer, a parent organization is provisioned successfully using the OID connector.
However, if one tries to create it's child organization the following error is seen:
DEBUG[XL_INTG.OID],com.thortech.xl.integration.OID.tcUtilOIDUserOperations:createOrganizationUnit(S,S) Returning with code: INVALID_NAMING_ERROR
The DEBUG messages in the log file show that the pObjDN for the child organization is constructed as follows
pObjDN = cn=oimchild,OU=oim01,dc=ab,dc=cd,,dc=ef
whereas it should be
pObjDN = cn=oimchild,cn=oim01,dc=ab,dc=cd,,dc=ef
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