Response Payload Object REQUIRED Description Unique Identifier, see 3.1 Yes, MAY be The list of Unique Identifiers of the repeated newly created objects. Template-Attribute, see 2.1.7.14 No An OPTIONAL list of object attributes with values that were not specified in the request, but have been implicitly set by the key management system. Table 232: Create Split Key Response Payload Join Split Key This operation requests the server to combine a list of Split Keys into a single Managed Cryptographic Object. The number of Unique Identifiers in the request SHALL be at least the value of the Split Key Threshold defined in the Split Keys. The request contains the Object Type of the Managed Cryptographic Object that the client requests the Split Key Objects be combined to form. If the Object Type formed is Secret Data, the client MAY include the Secret Data Type in the request. The response contains the Unique Identifier of the object obtained by combining the Split Keys. The server SHALL copy the Unique Identifier returned by this operation into the ID Placeholder variable. Request Payload Object REQUIRED Description Object Type, see 3.3 Yes Determines the type of object to be created. Unique Identifier, see 3.1 Yes, MAY be Determines the Split Keys to be repeated combined to form the object returned by the server. The minimum number of identifiers is specified by the Split Key Threshold field in each of the Split Keys. Secret Data Type No Determines which Secret Data type the Split Keys form. Template-Attribute, see 2.1.7.14 No Specifies desired object attributes using templates and/or individual attributes. Table 233: Join Split Key Request Payload Response Payload Object REQUIRED Description Unique Identifier, see 3.1 Yes The Unique Identifier of the object obtained by combining the Split Keys. Template-Attribute, see 2.1.7.14 No An OPTIONAL list of object attributes with values that were not specified in
Response Payload Object REQUIRED Description Unique Identifier, see 3.1 Yes, MAY be repeated The list of Unique Identifiers of the newly created objects. Template-Attribute, see 2.1.7.14 No An OPTIONAL list of object attributes with values that were not specified in the request, but have been implicitly set by the key management system. Table 232: Create Split Key Response Payload Join Split Key This operation requests the server to combine a list of Split Keys into a single Managed Cryptographic Object. The number of Unique Identifiers in the request SHALL be at least the value of the Split Key Threshold defined in the Split Keys. The request contains the Object Type of the Managed Cryptographic Object that the client requests the Split Key Objects be combined to form. If the Object Type formed is Secret Data, the client MAY include the Secret Data Type in the request. The response contains the Unique Identifier of the object obtained by combining the Split Keys. The server SHALL copy the Unique Identifier returned by this operation into the ID Placeholder variable. Request Payload Object REQUIRED Description Object Type, see 3.3 Yes Determines the type of object to be created. Unique Identifier, see 3.1 Yes, MAY be repeated Determines the Split Keys to be combined to form the object returned by the server. The minimum number of identifiers is specified by the Split Key Threshold field in each of the Split Keys. Secret Data Type No Determines which Secret Data type the Split Keys form. Template-Attribute, see 2.1.7.14 No Specifies desired object attributes using templates and/or individual attributes. Table 233: Join Split Key Request Payload Response Payload Object REQUIRED Description Unique Identifier, see 3.1 Yes The Unique Identifier of the object obtained by combining the Split Keys. Template-Attribute, see 2.1.7.14 No An OPTIONAL list of object attributes with values that were not specified in