For example, if a user's entry is removed from the directory and Referential Integrity is enabled, the server also removes the user from any groups of which the user is a member. If Referential Integrity is not enabled, the user remains a member of the group until manually removed by the administrator. This is an important feature if you are integrating the Directory Server with other products that rely on the directory for user and group management.
5.1. How Referential Integrity Works
When the Referential Integrity Postoperation plug-in is enabled, it performs integrity updates on specified attributes immediately after a delete or rename operation. By default, the Referential Integrity Postoperation plug-in is disabled.
Enable the Referential Integrity Postoperation plug-in only on one supplier replica in a multi-master replication environment, because the operations generated by the plug-in will be replicated. If you enable the plug-in on multiple masters, the servers have to manage and reapply already performed operations.
When a user or group entry is deleted, updated, renamed, or moved within the directory, the operation is logged to the Referential Integrity log file. For the distinguished names (DN) in the log file, Directory Server searches and updates in intervals the attributes set in the plug-in configuration:
For entries, marked in the log file as deleted, the corresponding attribute in the directory is deleted.
For entries, marked in the log file as updated, the corresponding attribute in the directory is updated.
For entries, marked in the log file as renamed or moved, the value of the corresponding attribute in the directory is renamed.
By default, when the Referential Integrity Postoperationplug-in is enabled, it performs integrity updates on the
seeAlso attributes immediately after a delete or rename operation. However, the behavior of the Referential Integrity Postoperation plug-in can be configured to suit the needs of the directory in several different ways:
Record Referential Integrity updates in the replication change log.
Modify the update interval.
Select the attributes to which to apply Referential Integrity.
Disable Referential Integrity.
All attributes used in referential integrity must
be indexed for presence and equality; not indexing those attributes results poor server performance for modify and delete operations.
See Section 13.2, “Creating Standard Indexes”
for more information about checking and creating indexes.