Processing an LDAP Modify RDN OperationChapter 7 Defining Functions for LDAP Operations 87• If the RDN of the entry contains attribute values that are not part of the entry(for example, if the RDN is “uid=bjensen” but the entry has no uid value or hasa different uid value), the function should call slapi_send_ldap_result() tosend the LDAP error code LDAP_NOT_ALLOWED_ON_RDN and should return -1.• If the requestor does not have permission to modify the entry (callslapi_access_allowed() to determine this), the function should callslapi_send_ldap_result() to send the LDAP error codeLDAP_INSUFFICIENT_ACCESS and should return -1.You should also verify that the ACI syntax for the entry is correct (callslapi_acl_check_mods() to determine this).If the modify function is successful, the function should callslapi_send_ldap_result() to send an LDAP_SUCCESS code back to the clientand should return 0.Processing an LDAP Modify RDN OperationWhen the Directory Server receives an LDAP modify RDN request from a client,the front-end gets the original DN of the entry, the new RDN, and (if the entry ismoving to a different location in the directory tree) the DN of the new parent of theentry.The front-end makes this information available to pre-operation andpost-operation plug-in functions in the form of parameters in a parameter block.Parameter ID Data Type DescriptionSLAPI_MODRDN_TARGET char * DN of the entry that you want torename.SLAPI_MODRDN_NEWRDN char * New RDN to assign to the entry.SLAPI_MODRDN_DELOLDRDN int Specifies whether or not you want todelete the old RDN. (0 means don’tdelete the old RDN; 1 means deletethe old RDN)SLAPI_MODRDN_NEWSUPERIOR char * DN of the new parent of the entry, ifthe entry is being moved to a newlocation in the directory tree.
