|
pure virtual |
Add the put batch item for a split key, which can be in the clear, encrypted and/or signed.
A successful startRequestMsg function must be called first. Note that a split key is typically a symmetric or private key.
Note, in Put requests the following fields defined in the startRequestMsg( P6KMIP_REQUESTPARAMS params ) call are not allowed: { pMaxResponseSize, pAsynchIndicator, pBatchErrorOption, pBatchOrderOption }. Simply set these fields to NULL in the "params" parameter in the startRequestMsg call.
Put (Section 5.2 KMIP spec), allows the KMIP server to push one of several objects to the client. This call is used to send one of the following wrapped objects: {SplitKey}
params | [ in ] group of parameters specific to the put request |
pKey | [ in ] The bits that compose the part of the split key to be sent (e.g., key split into 5 parts and the caller is encoding the 3rd part) |
pExtension | [ in ] optional can be NULL, vendor defined extension to the operation |
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 |