Add the revoke batch item to the current request message.
A successful startRequestMsg function must be called first.
Revoke (Section 4.20 KMIP spec), this operation requests to revoke a managed cryptographic object or an opaque object
- Parameters
-
| uniqueIdentifier | [ in ] optional uniqueIdentifier.pString can be NULL, the managed object to change the state. If NULL the server determines the object to query. |
| reason | [ in ] reason for revocation, see P6KMIP_REVOCATION structure definition |
| pOccurenceDate | [ in ] optional can be NULL, Compromise Occurrence Date, if the reason is "compromises" |
| pExtension | [ in ] optional can be NULL, vendor defined extension to the operation |
- Returns
| Success | P6R::eOk | |
| Failure | P6R::eNotInitialized | A successful call to intialize() must be made before calling this funciton. |
| P6R::eTooSmall | The configured buffer size in pPool is too small to hold the generated message. |
| P6R::eInvalidState | A successful call to startRequestMsg() must be made before calling this function. |
| P6R::eRange | pExtension->encodedExtension.length must be a multiple of 8, since encoded as the Vendor Extension Structure |
