Disabled User Gets Incorrectly Active by DBAT Trusted Recon
(Doc ID 2306043.1)
Last updated on OCTOBER 15, 2019
Applies to:Identity Manager Connector - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Using DBAT connector and seeing the following issue: For a disabled user in OIM created via trusted recon, during an update operation done via incremental trusted recon, the User's status changes to Active with the end data < Current date.
Have XL.UserDeleteDelayPeriod system property set to 60 days so user gets disabled first and then after 60 days gets deleted.
Steps to reproduce:
1. Create a new user in OIM by DBAT trusted Incremental recon with End Date < Current Date. This user will be Disabled status in OIM.
2. Update an attribute of this user in the target and run the incremental reconciliation (DBAT trusted recon).
The recon is making user Active in OIM even when End Date of user < Current Date.
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