This content has been marked as final. Show 5 replies
In the Bulk Post Process Event Handler, you can disable the user...
Make the Start Date one day more in future than the SYS DATE... But it will make it "Disable Until Start Date"
And by the way, share what happens when you try to achieve it by mapping the OIM Status attribute.... Any errors from logs etc...???
When you map Status attribute and then whatever status you set (Disabled, Active,Deleted) user is always created in 'Disabled' status so from that I see that something works wrong there.. Also when reconciliation operation is 'update' I do not want it to change the status so in this case the best way seems to disable user on postprocess event handler...
When I test it I will share the result ...
When I use UserManagerResult result = userManager.disable(entityId, true); methot on PostProcess event handler I get an error that user does not exist for the given entityId (the operation in bulk orchestration is 'CREATE').
As I understand when I make this checking the user is not yet created on OIM. What I should use here to disable the user when iti is first creating on OIM?
ps : I have checked the usr table if the user is created there with that user_key, and it was created..
Thanks in advance,
Edited by: 876017 on Nov 9, 2012 6:47 AM
Anyone who knows why userManager.disable(entityId, true) does not work on post process handler on trusted recon? When the opreation is 'CREATE' and try to call
userManager.disable(entityId, true) method it the entity is not found for the given entityId, it seems that at the time of the method call user is not still created at oim...How I can disable user on trsuted recon for 'CREATE' operation ? Any help is really strongly appreciated... We use 11g Release2..