jspωiki
Merge Authority

Merge Authority#

The Merge Authority is determined by the setting within the Novell IDM Driver Filters interface within iManager or Novell Designer and controls the operation of the Merge Processor.

Confusion Points#

A lot of people have a hard time separating the actions of the Novell IDM Driver Filters operations from the Merge Processor.

The Merge Processor, and therefore the Merge Authority are ONLY active when a Merge Operations is being processed. There is no operation of the Merge Authority on a non-merge operation.

DirXML Merge-Resync Process#

When the DirXML Engine uses the Merge Processor, the engine examines corresponding objects from both eDirectory and the connected system (e.g., AD). Depending on the Novell IDM Driver Filter and its Merge Authority settings, the engine will issue one or more modify commands in each directory (to eDirectory and to the application) to make the the two entries match the rules provided by the Novell IDM Driver Filters.

Migration and Merge Authority#

Issuing a migrate on an already-associated object will result in a merge (this is often referred to as a "re-sync").

If a match is found when migrating a non-associated object this will also result in a merge.

To determine if a transaction is a merge, you can evaluate the XML Attribute "from-merge" using this XPATH Example:

<if-xpath op="true">@from-merge = 'true'</if-xpath>

Default#

Not Synchronized on Either Channel#

If an attribute is not being synchronized on either channel, no merging occurs.

Data is only In One Side#

If an attribute is being s only In One Side and not the other, then all existing values on the destination for that channel are removed and replaced with the values from the source for that channel. If the source has multiple values and the destination can only accommodate a single value, then only one of the values is used on the destination side.

If the Application has a value for the attribute, and the Identity Vault is empty, then as a result of the merge the Identity Vault will be updated so that the two sides match. This works in the reverse situation as well.

If the Identity Vault has a value for the attribute, and the Application is empty, then as a result of the merge the Application will be updated so that the two sides match.

Synchronized on Both Channels - Both Single-Valued#

If an attribute is being synchronized in both channels and both sides can accommodate only a single value, the connected application acquires the Identity Vault values unless there is no value in the Identity Vault. If this is the case, the Identity Vault acquires the values from the connected application (if any).

Synchronized on Both Channels- One is Single-Valued#

If an attribute is being synchronized in both channels and only one side can accommodate multiple values, the single-valued side’s value is added to the multi-valued side if it is not already there. If there is no value on the single side, you can choose the value to add to the single side.

Synchronized on Both Channels - Both Multi-Valued#

Both sides will contain all values.

Identity Vault#

Behaves the same way as the default behavior if the attribute is being synchronized on the Subscriber channel and not on the Publisher channel. This is valid behavior when synchronizing on the Subscriber channel.

Application#

Behaves the same as the default behavior if the attribute is being synchronized on the Publisher channel and not on the Subscriber channel.

This is valid behavior when synchronizing on the Publisher channel.

None#

No merging occurs regardless of synchronization.

More Information#

There might be more information for this subject on one of the following: