Comments on: Getting Started with Provisioning http://www.wapshere.com/missmiis/getting-started-with-object-creation-and-deletion Adventures in identity management Tue, 07 Feb 2012 08:24:49 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Carol http://www.wapshere.com/missmiis/getting-started-with-object-creation-and-deletion/comment-page-1#comment-39 Carol Wed, 27 Aug 2008 05:10:22 +0000 http://www.wapshere.com/missmiis/?p=104#comment-39 The Provisioning code is invoked by any change to a metaverse object, including add, delete and attribute updates. It also runs both before an after a delete operation, which can lead to some unexpected errors if you weren't prepared for it. The provisioning code can't differentiate between types of updates - about all you can do, if you really must, is test for the MA that the change came from using the LastContributingMA property of the mventry. Good provisioning code design doesn't rely on any sequence of events. It should be able to take the entire data set, sync it all in any order, and arrive at the same result. This is the "steady-state" pricipal of MIIS, and is really a very powerful thing. The Provisioning code is invoked by any change to a metaverse object, including add, delete and attribute updates. It also runs both before an after a delete operation, which can lead to some unexpected errors if you weren’t prepared for it.

The provisioning code can’t differentiate between types of updates – about all you can do, if you really must, is test for the MA that the change came from using the LastContributingMA property of the mventry.

Good provisioning code design doesn’t rely on any sequence of events. It should be able to take the entire data set, sync it all in any order, and arrive at the same result. This is the “steady-state” pricipal of MIIS, and is really a very powerful thing.

]]> By: auzkhan http://www.wapshere.com/missmiis/getting-started-with-object-creation-and-deletion/comment-page-1#comment-37 auzkhan Tue, 26 Aug 2008 18:49:23 +0000 http://www.wapshere.com/missmiis/?p=104#comment-37 again...great post! :) at what events does the Sub Provision get invoked? when an object is projected in metaverse OR when an attribute flow rule updates a metaverse object attribute value OR when a metaverse object is deleted OR all of these events? If it gets invoked at more than one events, how can one differentiate between actually what caused it to invoke? for example, consider two data sources (CDS1 & CDS2 with MA1 & MA2) both containing users data having different attributes and whose data needs to be "aggregated" in metaverse and then exported into third data source (CDS3 - destination). MA1, being the master and most authoritative data source, is configured to "join", "project" & its attributes to be "imported" into the metaverse attributes. MA2 is only configured to "join" and its attributes to be "imported" into the metaverse attributes. So, in this scenario, MA1 can cause both objects to be created as well as updated in the metaverse, while MA2 can only cause objects to be updated in metaverse. If there is only one Sub Provision being invoked at both events (creation, updation), how can one identify which MA's activity (and exactly which activity - projection or attribute flow) invoked the Sub Provision, via source code? again…great post! :)

at what events does the Sub Provision get invoked? when an object is projected in metaverse OR when an attribute flow rule updates a metaverse object attribute value OR when a metaverse object is deleted OR all of these events?

If it gets invoked at more than one events, how can one differentiate between actually what caused it to invoke? for example, consider two data sources (CDS1 & CDS2 with MA1 & MA2) both containing users data having different attributes and whose data needs to be “aggregated” in metaverse and then exported into third data source (CDS3 – destination). MA1, being the master and most authoritative data source, is configured to “join”, “project” & its attributes to be “imported” into the metaverse attributes. MA2 is only configured to “join” and its attributes to be “imported” into the metaverse attributes. So, in this scenario, MA1 can cause both objects to be created as well as updated in the metaverse, while MA2 can only cause objects to be updated in metaverse.

If there is only one Sub Provision being invoked at both events (creation, updation), how can one identify which MA’s activity (and exactly which activity – projection or attribute flow) invoked the Sub Provision, via source code?

]]>