Describes an attribute of the enclosing <filter-class> that is used by a particular instance of an Identity Manager driver. The attr-name attribute specifies the name of an attribute in eDirectory.The publisher and subscriber attributes control whether this attribute is synchronized on the respective channels according to the following table. If the channel setting for the object class as a whole is ignored, then the setting for individual attributes is ignored.
The publisher and subscriber attributes control whether this attribute is synchronized on the respective channels according to the following table. If the channel setting for the object class as a whole is ignored, then the setting for individual attributes is ignored.
|
Value |
Description |
|---|---|
|
ignore |
Changes to this attribute are not reported or automatically synchronized. |
|
notify |
Changes to this attribute are reported but not automatically synchronized. |
|
sync |
Changes to this attribute are reported and automatically synchronized. |
|
reset |
Changes to this attribute are reported and triggers the attribute to be automatically reset to the values from the other channel. It is illegal for both Publisher and Subscriber to reset for the same attribute. |
The merge-authority attribute controls the behavior of the attribute during a merge operation according to the following table:
|
Value |
Behavior |
Valid |
|---|---|---|
|
default |
1. If an attribute is not being synchronized in either channel, then no merging occurs. 2. If an attribute is being synchronized in one channel 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, although it is undefined which of those values are used. 3. If an attribute is being synchronized in both channels and both sides can accommodate multiple values, then each side ends up with the union of values present on either side. 4. If an attribute is being synchronized in both channels and both sides can accommodate only a single value, the application ends up with the value from eDirectory unless there is no value in eDirectory. In this case eDirectory ends up with the value from the application (if any). 5. If an attribute is synchronized in both channels and only one side can accommodate multiple values then the single-valued side's value is added to the value from the multiple-value side if it is already there. If there is no value on the single-valued side one of the values (undefined) is added to the single-valued side. |
Always |
|
edir |
Has the same behavior as the default if the attributes are synchronized on the Subscriber channel and not on the Publisher channel. |
When synchronizing or notifying on the Subscriber channel |
|
app |
Has the same behavior as the default if the attributes are synchronized on the Publisher channel and not on the Subscriber channel. |
When synchronizing or notifying on the Publisher channel |
|
none |
No merging occurs regardless of synchronization. |
Always |
The publisher-optimize-modify attribute controls whether or not changes to this attribute are examined on the Publisher channel to determine the minimal change needed in the Identity Vault.
See <filter>.
EMPTY
|
Attribute |
Possible Values |
Default Value |
|---|---|---|
|
attr-name |
CDATA Name of the attribute. |
#REQUIRED |
|
merge-authority |
default | edir | app | none Flag that controls how this attribute is merged. |
default |
|
publisher |
ignore | notify | sync | reset Flag that controls Publisher channel synchronization. |
ignore |
|
publisher-optimize-modify |
true | false Flag that controls optimization of modifications on the Subscriber channel. |
true |
|
subscriber |
ignore | notify | sync | reset Flag that controls Subscriber channel synchronization. |
ignore |
Empty
|
Element |
Description |
|---|---|
|
Behavior of an object class. |