3.1.4.16 RRPC_FWDeleteAllConnectionSecurityRules (Opnum 15)
The RRPC_FWDeleteAllConnectionSecurityRules method requests the server to delete all the connection security rules in the policy contained in the policy store referenced by the handle specified in the hPolicy parameter.
-
unsigned long RRPC_FWDeleteAllConnectionSecurityRules( [in] FW_CONN_HANDLE rpcConnHandle, [in] FW_POLICY_STORE_HANDLE hPolicy );
rpcConnHandle: This parameter is an RPC binding handle that connects to the RPC interface of the Firewall and Advanced Security Protocol.
hPolicy: This input parameter is an FW_POLICY_STORE_HANDLE data type. The data type MUST contain an opened policy store handle, successfully opened with the RRPC_FWOpenPolicyStore (Opnum 0) method. The handle MUST have read/write access rights.
Return Values: The method returns 0 if successful; if failed, it returns a nonzero error code. The field can take any specific error code value, as specified in [MS-ERREF]. The following return values are common.
-
Return value/code
Description
0x00000032
ERROR_NOT_SUPPORTED
The specified store does not support this method; the store might be read-only.
0x00000005
ERROR_ACCESS_DENIED
The hPolicy handle was not opened with read/write access rights. The error is also returned if the client does not have the required credentials to call the method.
Exceptions Thrown: No exceptions are thrown beyond those thrown by the underlying RPC protocol, as specified in [MS-RPCE]. If any lower-layer errors are reported by RPC exception, this exception is converted to an error code and reported to higher-layer protocols via the return value.
This method deletes all connection security rules in the connection security linked list of the memory representation of the store being modified. It also writes through and deletes all rules from the disk representation. If called on an online store, no connection security rules are enforced after the method returns.
The server MUST validate that the client is authorized to perform the requested operation (as defined in section 3.1.4) before executing this method.