My Oracle Support Banner

OID to Portal DIP Provisioning Is Failing - Re-created User Unable To Login To Portal (Doc ID 1229203.1)

Last updated on AUGUST 30, 2023

Applies to:

Oracle Internet Directory - Version 10.1.2 to 10.1.4 [Release 10gR2 to 10gR3]
Information in this document applies to any platform.

Symptoms

When users are deleted and recreated in Oracle Internet Directory (OID), the users are unable to login to Portal: there is a GUID conflict because the Portal user is not properly removed by OID Directory Integration and Provisioning (DIP).

The DIP provisioning profile trace log $ORACLE_HOME/ldap/odi/log/portal*_E.trc does not report any errors. However the provisioning profile audit log $ORACLE_HOME/ldap/odi/log/portal*_E.aud has entries that indicate that the delete user event in OID was not provisioned because the user was not found in the Portal repository.

The message 'Event Not propagated' is shown in the audit log.

Example of Portal provisioning audit log:


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
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.