My Oracle Support Banner

Oracle Access Manager (OAM) Integration with Oracle Identity Manager (OIM) SSO User Full/Incremental Reconciliation Job not Locking Locked User Created in Oracle Unified Directory (OUD) (Doc ID 2532433.1)

Last updated on FEBRUARY 21, 2020

Applies to:

Identity Manager - Version 12.2.1.3.180109 and later
Information in this document applies to any platform.

Symptoms

A user is created in OUD with the attribute oblockedOn set to sysdate

 

 

We then run any of the following two schedule jobs SSO User Full Reconciliation or SSO User Incremental Reconciliation to reconcile the user into OIM

 

 

The user is then reconciled into OIM.

 

 

The expectation at this stage is that, as the user was created in OUD with the attribute oblockedon set, that the user in OIM is locked.

As we can see in the above screenshot the user is not locked.

Is this expected behavior?

Yes. Setting only the attribute oblockedon in a user entry will not lock the user in OIM.

 

 

 

 

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.