DIP Import Creates Users in the Wrong Container
(Doc ID 973481.1)
Last updated on AUGUST 30, 2023
Applies to:
Oracle Internet Directory - Version 10.1.2 to 10.1.4.3 [Release 10gR2 to 10gR3]Information in this document applies to any platform.
Symptoms
DIP import to OID has been configured with multiple DomainRules for specific containers
For example:
DomainRules
OU=<OU>,OU=Users,DC=<AD_DOMAIN>,DC=com:ou=<OU>,cn=users,dc=<COMPANY>,dc=com:cn%,ou=<OU>,cn=users,dc=<COMPANY>,dc=com
OU=Users,DC=<AD_DOMAIN>,DC=com:cn=users,dc=<COMPANY>,dc=com:cn%,cn=users,dc=<COMPANY>,dc=com
A user created in this AD container:
OU=<OU>,OU=Users,DC=<AD_DOMAIN>,DC=com
is then synchronized into this OID container
cn=users,dc=<COMPANY>,dc=com
contrary to expectations, according to the DomainRules.
Changes
New DomainRule added for the OU=Admin child container
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |