From f4dd34d24c22926b76da6f6e1d9f4c471ec2b2da Mon Sep 17 00:00:00 2001
From: rhaggard <rhaggard@localhost>
Date: Fri, 01 Feb 2008 17:30:23 +0000
Subject: [PATCH] commiting configuration XML files after adding info from the old config guide to be incorporated in the new generated config reference

---
 opends/src/admin/defn/org/opends/server/admin/std/EntryUUIDPluginConfiguration.xml |   20 +++++++++++++++++++-
 1 files changed, 19 insertions(+), 1 deletions(-)

diff --git a/opends/src/admin/defn/org/opends/server/admin/std/EntryUUIDPluginConfiguration.xml b/opends/src/admin/defn/org/opends/server/admin/std/EntryUUIDPluginConfiguration.xml
index 90493b7..ffc871d 100644
--- a/opends/src/admin/defn/org/opends/server/admin/std/EntryUUIDPluginConfiguration.xml
+++ b/opends/src/admin/defn/org/opends/server/admin/std/EntryUUIDPluginConfiguration.xml
@@ -32,8 +32,26 @@
   <adm:synopsis>
     The
     <adm:user-friendly-name />
-    is used to generate values for the entryUUID operational attribute
+    generates values for the entryUUID operational attribute
     whenever an entry is added via protocol or imported from LDIF.
+    The entryUUID plug-in ensures that all entries 
+    added to the server, whether through an LDAP add operation or via 
+    an LDIF import, are assigned an entryUUID operational attribute if 
+    they do not already have one. The entryUUID attribute contains a 
+    universally unique identifier that can be used to identify an entry 
+    in a manner that does not change (even in the event of a modify DN 
+    operation). This plug-in generates a random UUID for entries created 
+    by an add operation, but the UUID is constructed from the DN of the 
+    entry during an LDIF import (which means that the same LDIF file 
+    can be imported on different systems but still get the same value 
+    for the entryUUID attribute). This behavior is based on the 
+    specification contained in RFC 4530. The implementation for the 
+    entry UUID plug-in is contained in the 
+    org.opends.server.plugins.EntryUUIDPlugin class. It must be 
+    configured with the preOperationAdd and ldifImport plug-in types, 
+    but it does not have any other custom configuration. This 
+    plug-in must be enabled in any directory that is intended to be used 
+    in a synchronization environment.  
   </adm:synopsis>
   <adm:profile name="ldap">
     <ldap:object-class>

--
Gitblit v1.10.0