Add the re-key batch item to the current request message.
A successful startRequestMsg function must be called first.
Re-key (Section 4.4 KMIP spec), allows the KMIP client to request the re-generation of a symmetric key to replace an existing key.
- Parameters
-
| uniqueIdentifier | [ in ] optional uniqueIdentifier.pString can be NULL, pointer to the symmetric key to replace |
| pOffset | [ in ] optional can be NULL, an interval value to indicate the difference between the initialization date and the activation date |
| pAttrbutes | [ in ] optional can be NULL, any of the defined attributes to be associated with the registered object (e.g., Object Group) |
| 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 |
