Table of Contents
Advertisement
•
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 has
a different uid value), the function should call
send the LDAP error code
•
If the requestor does not have permission to modify the entry (call
slapi_access_allowed()
slapi_send_ldap_result()
LDAP_INSUFFICIENT_ACCESS
You should also verify that the ACI syntax for the entry is correct (call
slapi_acl_check_mods()
If the modify function is successful, the function should call
slapi_send_ldap_result()
and should return 0.
Processing an LDAP Modify RDN Operation
When 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 is
moving to a different location in the directory tree) the DN of the new parent of the
entry.
The front-end makes this information available to pre-operation and
post-operation plug-in functions in the form of parameters in a parameter block.
Parameter ID
SLAPI_MODRDN_TARGET
SLAPI_MODRDN_NEWRDN
SLAPI_MODRDN_DELOLDRDN
SLAPI_MODRDN_NEWSUPERIOR
slapi_send_ldap_result()
LDAP_NOT_ALLOWED_ON_RDN
to determine this), the function should call
to send the LDAP error code
and should return -1.
to determine this).
to send an
LDAP_SUCCESS
Data Type
Description
DN of the entry that you want to
char *
rename.
New RDN to assign to the entry.
char *
Specifies whether or not you want to
int
delete the old RDN. (0 means don't
delete the old RDN; 1 means delete
the old RDN)
DN of the new parent of the entry, if
char *
the entry is being moved to a new
location in the directory tree.
Chapter 7
Defining Functions for LDAP Operations
Processing an LDAP Modify RDN Operation
and should return -1.
code back to the client
to
87
Advertisement
Table of Contents
