Kill connection extended operation
The kill connection extended operation explains its use with the server and provides the results.
- Description
- The Kill connection extended operation requests that the server
to stop the specified connections. Connections can be stopped based
on the following parameters:
- Connection IP
- Connection DN
- Combination of IP and DN
- All connections
Note: This extended operation is always enabled. - Request
-
- OID
- 1.3.18.0.2.12.35
- Syntax
-
For a DN-specific or IP-specific request, only one set of type and value is needed. For a combination DN or IP request, both sets of type and value are needed. If there is no value that is specified, all connections are stopped.ReqType ::= ENUMERATED { DN (1), IP (2) } RequestValue ::= SEQUENCE { SET {type ReqType value Directory String} OPTIONAL SET {type ReqType value Directory String} OPTIONAL }
- Response
-
- OID
- 1.3.18.0.2.12.36
- Syntax
-
Each DN has its own return code. If the return code is not SUCCESS, a DN of zero length is returned for every DN passed in on the original request. The order of DN values in the response matches the order of DN values that are passed in the request.ResponseValue ::= { int numberKilled int numberPending }
- Behavior
- This extended operation stops the requested connections.The following persons are enabled to call the extended operation:
- Primary Directory Administrator
- Local Administration Group members with
DirDataAdminrole - Global Administrators
Note: If the extended operation is called by a user who does not have access, LDAP_INSUFFICIENT_ACCESS is returned.This extended operation has the following possible return codes:- LDAP_SUCCESS
- LDAP_NO_SUCH_OBJECT
- LDAP_INSUFFICIENT_ACCESS
- LDAP_INVALID_DN_SYNTAX
- LDAP_OTHER
- LDAP_PROTOCAL_ERROR
- Scope
- The extended operation affects only the current operation.
- Auditing
- The DN or IP or both are provided:
If the DN or the IP is not present, then the request was to stop all connections.DN: DN IP: IP