Tuesday, 17 August 2010

When an attribute of an OIM user is changed a trigger can be started. The first thing that is triggered is the post update trigger of the Data Object. This will trigger a check of the LOOKUP.USR.TRIGGER lookup tables.When a field defined in this lookup table is changed the process defined in the decode field of this table is triggered. This means all the processes on all the resource objects exactly named as in the decode field are triggered. This way a password change on the OIM user atribute could change password change processes be triggered on all resource objects. As long as the resource objects tasks are exactly named like in the lookup table is defined.

Watch out for circular triggers in the post update trigger. When the post update trigger makes an update of the attribute it will recursively trigger itself. When no end point in this trigger process is defined the application server will go down because all the resources will be used in this process.

2 comments:

The post update trigger updates the field on which the trigger is, that ways starting the trigger, that would do an update that would again trigger the post update trigger.....etc etc etc.This recursive process would bring down your application server.

By the way soory for the late reply, I didn't receive your post notification.

About the Blogger of this page

I'm the director for Product Security Personal health of Philips. Before I worked as the Corporate Security Officer at TomTom, responsible for "all things security" ranging from physical security, investigations, whistle blower, to information security operations and security in the development life cycles of the different units (Product Security).
I have worked as a solution, technical and enterprise
Architect with specialism in security, performance and high availiability for Oracle Consulting for more than 12 years. In 2009 I was the Corporate Information Security Officer at Royal Vopak. I've worked for boutique Identity Management company Everett.