OID to Portal DIP Provisioning Is Failing - Re-created User Unable To Login To Portal
(Doc ID 1229203.1)
Last updated on OCTOBER 03, 2019
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.
***Checked for relevance on 16-AUG-2012***
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:
User Exists Check - UID : <FIRSTNAME>.<LASTNAME> ,GUID (<GUID_VALUE>) - Response : 0
Event Not propagated..
40508 : Success : DELETE : cn=<FIRSTNAME>.<LASTNAME>,cn=users,dc=<COMPANY>,dc=com
Fri Sep 03 11:38:37 SAST 2010 - Audit Log End
Steps to reproduce
1. Create a user in OID.
2. Login to Portal as the new user.
3. Delete the user in OID.
4. Create the user in OID again.
5. Try to login to Portal as the user, an error occurs as follows:
Internal error (WWC-00006)
Unexpected error encountered in wwsec_app_priv.process_signon (User-Defined
There is a conflict with your assigned user name. There is a user entry with
this name, but with a different globally unique identifier, which must be
resolved before you can log on with this name. Please inform your
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