Lines Matching refs:Modify

74       4.6. Modify Operation ..........................................31
77       4.9. Modify DN Operation .......................................34
1696 4.6.  Modify Operation
1698    The Modify operation allows a client to request that a modification
1699    of an entry be performed on its behalf by a server.  The Modify
1712    Fields of the Modify Request are:
1757    Upon receipt of a Modify Request, the server attempts to perform the
1758    necessary modifications to the DIT and returns the result in a Modify
1763    The server will return to the client a single Modify Response
1766    for atomicity in applying the list of modifications in the Modify
1768    been performed if the Modify Response received indicates any sort of
1770    the Modify Response indicates successful completion of the Modify
1772    determined by the client if the Modify Response was not received
1773    (e.g., the LDAP session was terminated or the Modify operation was
1777    rules or other data model constraints.  The Modify operation cannot
1781    notAllowedOnRDN result code.  The Modify DN operation described in
1878 4.9.  Modify DN Operation
1880    The Modify DN operation allows a client to change the Relative
1882    a subtree of entries to a new location in the Directory.  The Modify
1891    Fields of the Modify DN Request are:
1923    the name change and return the result in the Modify DN Response,
3551 C.1.21.  Section 4.6 (Modify Operation)
3572 C.1.23.  Section 4.9 (Modify DN Operation)
3574    - Required servers to not dereference aliases for Modify DN.  This
3577    - Allow Modify DN to fail when moving between naming contexts.