Dynamic update requests extended operation

Edit online

The dynamic update request extended operation explains its use with the server and provides the results.

Description
The Dynamic update extended operation requests that the server reread its configuration.
Note: This extended operation is always enabled.
Request
OID
1.3.18.0.2.12.28
Syntax
RequestValue ::= SEQUENCE {
	action	INTEGER {rereadFile(0), 
         rereadAttribute(1),
         rereadEntry(2),
         rereadSubtree(3)};
	entry			[0]	DistinguishedName OPTIONAL;
	attribute		[1]	DirectoryString OPTIONAL;
}
Response
OID
1.3.18.0.2.12.29
Syntax
There is no response value.
Behavior
This extended operation forces the server to reread the configuration file. The request can be to reread the entire file, a subtree, an entry, or a specific attribute. When the server receives the request, the server reads the configuration file again. It updates all the internal server settings to use the new settings from the configuration file. Only the dynamic attributes are read again.
Only Primary Directory Administrator and Local Administration Group members with DirDataAdmin role are enabled to call this extended operation. Local Administration Group members cannot update attributes of other Local Administration Group members.
Note: If the control is sent by a user who does not have access, LDAP_INSUFFICIENT_ACCESS is returned.
This control has the following possible return codes:
  • LDAP_SUCCESS
  • LDAP_UNDEFINED_TYPE
  • LDAP_INSUFFICIENT_ACCESS
  • LDAP_INVALID_SYNTAX
  • LDAP_INVALID_DN_SYNTAX
  • LDAP_UNWILLING_TO_PERFORM
  • LDAP_OBJECT_CLASS_VIOLATION
  • LDAP_OTHER
  • LDAP_PROTOCOL_ERROR
  • LDAP_NO_SUCH_ATTRIBUTE
  • LDAP_NO_SUCH_OBJECT
  • LDAP_NO_MEMORY

This extended operation is supported by the Administration Server.

Scope
This extended operation causes the server to reread its configuration, which can affect subsequent operations.
Auditing
The Scope is provided along with the entry dn, or attribute when necessary. 
Scope: Scope Value
where Scope Value can be one of the following values:
  • Entire - entire configuration file
  • Single - for a single attribute
  • Entry - for an entry
  • Subtree - for a subtree

DN: Entry DN – This DN is required for Single, Entry, and Subtree.

Attribute: Attribute – This attribute is required for Single only.