KMIP Storage Array with Self-Encrypting Drives Profile Version 1.0 OASIS Standard 19 May 2015 Specification URIs This version: http://docs.oasis-open.org/kmip/kmip-sa-sed-profile/v1.0/os/kmip-sa-sed-profile-v1.0-os.doc (Authoritative) http://docs.oasis-open.org/kmip/kmip-sa-sed-profile/v1.0/os/kmip-sa-sed-profile-v1.0-os.html http://docs.oasis-open.org/kmip/kmip-sa-sed-profile/v1.0/os/kmip-sa-sed-profile-v1.0-os.pdf Previous version: http://docs.oasis-open.org/kmip/kmip-sa-sed-profile/v1.0/csprd01/kmip-sa-sed-profile-v1.0-csprd01.doc (Authoritative) http://docs.oasis-open.org/kmip/kmip-sa-sed-profile/v1.0/csprd01/kmip-sa-sed-profile-v1.0-csprd01.html http://docs.oasis-open.org/kmip/kmip-sa-sed-profile/v1.0/csprd01/kmip-sa-sed-profile-v1.0-csprd01.pdf Latest version: http://docs.oasis-open.org/kmip/kmip-sa-sed-profile/v1.0/kmip-sa-sed-profile-v1.0.doc (Authoritative) http://docs.oasis-open.org/kmip/kmip-sa-sed-profile/v1.0/kmip-sa-sed-profile-v1.0.html http://docs.oasis-open.org/kmip/kmip-sa-sed-profile/v1.0/kmip-sa-sed-profile-v1.0.pdf Technical Committee: OASIS Key Management Interoperability Protocol (KMIP) TC Chairs: Saikat Saha ( [email protected] ), Oracle Tony Cox ( [email protected] ), Cryptsoft Pty Ltd. Editors: Tim Hudson ( [email protected] ), Cryptsoft Pty Ltd. Mahadev Karadigudda ( [email protected] ), NetApp Related work: This specification is related to: � Key Management Interoperability Protocol Profiles Version 1.0. Edited by Robert Griffin and Subhash Sankuratripati. Latest version: http://docs.oasis-open.org/kmip/profiles/v1.0/kmip-profiles-1.0.html . � Key Management Interoperability Protocol Profiles Version 1.1 . Edited by Robert Griffin and Subhash Sankuratripati. Latest version: http://docs.oasis-open.org/kmip/profiles/v1.1/kmip-profiles-v1.1.html . � Key Management Interoperability Protocol Profiles Version 1.2 . Edited by Tim Hudson and Robert Lockhart. Latest version: http://docs.oasis-open.org/kmip/profiles/v1.2/kmip-profiles-v1.2.html . � Key Management Interoperability Protocol Specification Version 1.1 . Edited by Robert Haas and Indra Fitzgerald. Latest version: http://docs.oasis-open.org/kmip/spec/v1.1/kmip-spec-v1.1.html . � Key Management Interoperability Protocol Specification Version 1.2 . Edited by Kiran Thota and Kelley Burgin. Latest version: http://docs.oasis-open.org/kmip/spec/v1.2/kmip-spec-v1.2.html . � Key Management Interoperability Protocol Test Cases Version 1.2 . Edited by Tim Hudson and Faisal Faruqui. Latest version: http://docs.oasis-open.org/kmip/testcases/v1.2/kmip-testcases-v1.2.html . � Key Management Interoperability Protocol Usage Guide Version 1.2 . Edited by Indra Fitzgerald and Judith Furlong. Latest version: http://docs.oasis-open.org/kmip/ug/v1.2/kmip-ug-v1.2.html . Abstract: Describes a profile for Storage Arrays with Self-Encrypting Drives as KMIP clients interacting with KMIP servers Status: This document was last revised or approved by the membership of OASIS on the above date. The level of approval is also listed above. Check the �Latest version� location noted above for possible later revisions of this document. Any other numbered Versions and other technical work produced by the Technical Committee (TC) are listed at https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=kmip#technical . Technical Committee members should send comments on this specification to the Technical Committee�s email list. Others should send comments to the Technical Committee by using the � Send A Comment � button on the Technical Committee�s web page at https://www.oasis-open.org/committees/kmip/ . For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page ( https://www.oasis-open.org/committees/kmip/ipr.php . Citation format: When referencing this specification the following citation format should be used: [kmip-sa-sed-v1.0] KMIP Storage Array with Self-Encrypting Drives Profile Version 1.0 . Edited by Tim Hudson and Mahadev Karadigudda. 19 May 2015. OASIS Standard. http://docs.oasis-open.org/kmip/kmip-sa-sed-profile/v1.0/os/kmip-sa-sed-profile-v1.0-os.html . Latest version: http://docs.oasis-open.org/kmip/kmip-sa-sed-profile/v1.0/kmip-sa-sed-profile-v1.0.html . Notices Copyright � OASIS Open 2015. All Rights Reserved. All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so. OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims. The name "OASIS" is a trademark of OASIS , the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see https://www.oasis-open.org/policies-guidelines/trademark for above guidance. Table of Contents 1 ������� Introduction . 5 1.1 Terminology . 5 1.2 Normative References . 5 2 ������� Storage Array with Self-Encrypting Drives Profile . 6 2.1 Authentication Suite . 6 2.2 Storage Array with Self-Encrypting Drives - Client 6 2.3 Storage Array with Self-Encrypting Drives - Server 6 3 ������� Storage Array with Self-Encrypting Drives Test Cases . 8 3.1 Mandatory Test Cases KMIP v1.0 . 8 3.1.1 SASED-M-1-10 - Configuration . 8 3.1.2 SASED-M-2-10 - Register the authentication key . 9 3.1.3 SASED-M-3-10 - Retrieve Authentication Key . 12 3.2 Mandatory Test Cases KMIP v1.1 . 17 3.2.1 SASED-M-1-11 - Configuration . 17 3.2.2 SASED-M-2-11 - Register the authentication key . 18 3.2.3 SASED-M-3-11 - Retrieve Authentication Key . 22 3.3 Mandatory Test Cases KMIP v1.2 . 27 3.3.1 SASED-M-1-12 - Configuration . 27 3.3.2 SASED-M-2-12 - Register the authentication key . 28 3.3.3 SASED-M-3-12 - Retrieve Authentication Key . 31 4 ������� Conformance . 37 4.1 Storage Array with Self Encrypting Drive Client KMIP v1.0 Profile Conformance . 37 4.2 Storage Array with Self Encrypting Drive Client KMIP v1.1 Profile Conformance . 37 4.3 Storage Array with Self Encrypting Drive Client KMIP v1.2 Profile Conformance . 37 4.4 Storage Array with Self Encrypting Drive Server KMIP v1.0 Profile Conformance . 37 4.5 Storage Array with Self Encrypting Drive Server KMIP v1.1 Profile Conformance . 37 4.6 Storage Array with Self Encrypting Drive Server KMIP v1.2 Profile Conformance . 37 4.7 Permitted Test Case Variations . 38 4.7.1 Variable Items . 38 4.7.2 Variable behavior 39 Appendix A. ������ Acknowledgments . 40 Appendix B. ������ KMIP Specification Cross Reference . 43 Appendix C. ������ Revision History . 48 1 Introduction For normative definition of the elements of KMIP see the KMIP Specification [KMIP-SPEC] and the KMIP Profiles [KMIP-PROF]. This profile defines the necessary KMIP functionality that a Storage Array with Self-Encrypting Drives �operating as a KMIP client SHALL use and a KMIP server conforming to this profile SHALL support in order to interoperate in conformance with this profile. 1.1 Terminology The key words �MUST�, �MUST NOT�, �REQUIRED�, �SHALL�, �SHALL NOT�, �SHOULD�, �SHOULD NOT�, �RECOMMENDED�, �MAY�, and �OPTIONAL� in this document are to be interpreted as described in [RFC2119] . Authentication Key A secret used by self-encrypting drives to verify authenticity of the client before allowing the drive to perform sensitive operations. 1.2 Normative References [RFC2119] �������������� Bradner, S., �Key words for use in RFCs to Indicate Requirement Levels�, BCP 14, RFC 2119, March 1997. http://www.ietf.org/rfc/rfc2119.txt . [KMIP-ENCODE]���� KMIP Additional Message Encodings Version 1.0. Edited by Tim Hudson. Latest version: http://docs.oasis-open.org/kmip/kmip-addtl-msg-enc/v1.0/kmip-addtl-msg-enc-v1.0.doc . [KMIP-SPEC]��������� One or more of [KMIP-SPEC-1_0], [KMIP-SPEC-1_1], [KMIP-SPEC-1_2] [KMIP-SPEC-1_0]��� Key Management Interoperability Protocol Specification Version 1.0 http://docs.oasis-open.org/kmip/spec/v1.0/os/kmip-spec-1.0-os.doc OASIS Standard, October 2010. [KMIP-SPEC-1_1] ��� Key Management Interoperability Protocol Specification Version 1.1. http://docs.oasis-open.org/kmip/spec/v1.1/os/kmip-spec-v1.1-os.doc OASIS Standard. 24 January 2013. [KMIP-SPEC-1_2]��� Key Management Interoperability Protocol Specification Version 1.2 . Edited by Kiran Thota and Kelley Burgin. Latest version: http://docs.oasis-open.org/kmip/spec/v1.2/kmip-spec-v1.2.doc . [KMIP-PROF]��������� One or more of [KMIP-PROF-1_0], [KMIP-PROF-1_1], [KMIP-PROF-1_2] [KMIP-PROF-1_0]��� Key Management Interoperability Protocol Profiles Version 1.0. � http://docs.oasis-open.org/kmip/profiles/v1.0/os/kmip-profiles-1.0-os.doc OASIS Standard. 1 October 2010.� [KMIP-PROF-1_1]��� Key Management Interoperability Protocol Profiles Version 1.1 http://docs.oasis-open.org/kmip/profiles/v1.1/os/kmip-profiles-v1.1-os.doc OASIS Standard 01. 24 January 2013. [KMIP-PROF-1_2]��� Key Management Interoperability Protocol Profiles Version 1.2 . Edited by Tim Hudson and Robert Lockhart. Latest version: http://docs.oasis-open.org/kmip/profiles/v1.2/kmip-profiles-v1.2.doc . 2 Storage Array with Self-Encrypting Drives Profile The Storage Array with Self-Encrypting Drives Profile is a storage array containing self-encrypting drives operating as a KMIP client interacting with a KMIP server. 2.1 Authentication Suite Implementations conformant to this profile SHALL support at least one of the Authentication Suites defined within [KMIP-PROF]. The establishment of the trust relationship between the KMIP client and the KMIP server is the same as the defined base profiles for the version of the profile supported. 2.2 Storage Array with Self-Encrypting Drives - Client KMIP clients conformant to this profile under [KMIP-SPEC-1_0]: SHALL conform to the [KMIP-SPEC-1_0] KMIP clients conformant to this profile under [KMIP-SPEC-1_1]: SHALL conform to the Baseline Client Clause (section 5.12) of [KMIP-PROF-1_1] KMIP clients conformant to this profile under [KMIP-SPEC-1_2]: SHALL conform to the Baseline Client (section 5.2) of [KMIP-PROF-1_2] KMIP clients conformant to this profile: SHOULD NOT use a C ustom Attribute [KMIP-SPEC] that duplicates information that is already in standard Attributes [KMIP-SPEC] 2.3 Storage Array with Self-Encrypting Drives - Server KMIP servers conformant to this profile under [KMIP-SPEC-1_0]: SHALL conform to the Conformance clauses for a KMIP Server (section 12.1) of [KMIP-SPEC-1_0] KMIP servers conformant to this profile under [KMIP-SPEC-1_1]: SHALL conform to the Baseline Server Clause (section 5.2) of [KMIP-PROF-1_1] KMIP servers conformant to this profile under [KMIP-SPEC-1_2]: SHALL conform to the Baseline Server (section 5.1) of [KMIP-PROF-1_2] KMIP servers conformant to this profile SHALL: SHALL support the following Objects [KMIP-SPEC] Template [KMIP-SPEC] Secret Data [KMIP-SPEC] SHALL support the following Attributes [KMIP-SPEC] Custom Attribute [KMIP SPEC] SHALL support the following client-to-server operations: Register [KMIP-SPEC] SHALL support the following Message Encoding [KMIP-SPEC]:: Secret Data Type Enumeration [KMIP-SPEC] value: i. Password Object Type Enumeration [KMIP-SPEC] values: i. Secret Data ii. Template Name Type Enumeration [KMIP-SPEC] value: i. Uninterpreted Text String SHALL support C ustom Attribute [KMIP-SPEC] with the following data types and properties: TextString SHALL support a minimum length of 64 characters for C ustom Attribute [KMIP-SPEC] and Name [KMIP-SPEC] values where the attribute type is of variable length. SHALL support a minimum of 10 C ustom Attribute [KMIP-SPEC] per managed object SHALL support a minimum of 64 characters in C ustom Attribute [KMIP-SPEC] names MAY support any clause within [KMIP-SPEC] provided it does not conflict with any other clause within this section 2.2 MAY support extensions outside the scope of this standard (e.g., vendor extensions, conformance clauses) that do not contradict any KMIP requirements. 3 Storage Array with Self-Encrypting Drives Test Cases The test cases define a number of request-response pairs for KMIP operations. Each test case is provided in the XML format specified in [KMIP-ENCODE] intended to be both human-readable and usable by automated tools. The time sequence (starting from 0) for each request-response pair is noted and line numbers are provided for ease of cross-reference for a given test sequence. Each test case has a unique label (the section name) which includes indication of mandatory (-M-) or optional (-O-) status and the protocol version major and minor numbers as part of the identifier. The test cases may depend on a specific configuration of a KMIP client and server being configured in a manner consistent with the test case assumptions. Where possible the flow of unique identifiers between tests, the date-time values, and other dynamic items are indicated using symbolic identifiers � in actual request and response messages these dynamic values will be filled in with valid values. Note: the values for the returned items and the custom attributes are illustrative. Actual values from a real client system may vary as specified in section 4.7. 3.1 Mandatory Test Cases KMIP v1.0 3.1.1 SASED-M-1-10 - Configuration Determine server configuration details including operations supported (only the mandatory operations are listed in the response example), objects supported (only the mandatory objects types are listed in the response example), and optional server information. 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0012 0013 0014 0015 0016 0017 # TIME 0 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Query" /> ��� <RequestPayload> � ���� <QueryFunction type= "Enumeration" value= "QueryOperations" /> ����� <QueryFunction type= "Enumeration" value= "QueryObjects" /> ��� �� <QueryFunction type= "Enumeration" ���������������������������� value= "QueryServerInformation" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0018 0019 0020 0021 0022 0023 0024 0025 0026 0027 0028 0029 0030 0031 0032 0033 0034 0035 0036 0037 0038 0039 0040 0041 0042 0043 0044 0045 0046 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:03+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Query" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <Operation type= "Enumeration" value= "Query" /> ����� <Operation type= "Enumeration" value= "Locate" /> ����� <Operation type= "Enumeration" value= "Destroy" /> ����� <Operation type= "Enumeration" value= "Get" /> ����� <Operation type= "Enumeration" value= "Register" /> ����� <Operation type= "Enumeration" value= "GetAttributes" /> ����� <Operation type= "Enumeration" value= "GetAttributeList" /> ����� <Operation type= "Enumeration" value= "AddAttribute" /> ����� <ObjectType type= "Enumeration" value= "SecretData" /> ����� <ObjectType type= "Enumeration" value= "Template" /> ����� <VendorIdentification type= "TextString" value= "server-vendor.com" /> ����� <ServerInformation> � ���� </ServerInformation> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 3.1.2 SASED-M-2-10 - Register the authentication key A template is created and the secret data for the authentication key is then registered. The server must allow the registration of managed objects for Object Groups either by allowed arbitrary values for Object Groups or by pre-configuration of specific Object Groups prior to the storage array registering the authentication key.� The authentication key may be a new authentication key or a replacement authentication key. 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 0020 0021 0022 0023 0024 0025 # TIME 0 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <RequestPayload> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Name" /> ������� <AttributeValue> � ��� ����� <NameValue type= "TextString" value= "SASED-M-2-10-template1" /> ��������� <NameType type= "Enumeration" ����������������������������� value= "UninterpretedTextString" /> ������� </AttributeValue> � ���� </Attribute> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Type" /> ������� <AttributeValue type= "Enumeration" value= "Template" /> ����� </Attribute> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0026 0027 0028 0029 0030 0031 0032 0033 0034 0035 0036 0037 0038 0039 0040 0041 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0042 0043 0044 0045 0046 0047 0048 0049 0050 0051 0052 0053 0054 0055 0056 0057 0058 0059 0060 0061 0062 0063 0064 0065 0066 0067 0068 0069 0070 0071 0072 0073 0074 0075 0076 0077 0078 0079 # TIME 1 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <RequestPayload> � ���� <ObjectType type= "Enumeration" value= "Template" /> ����� <TemplateAttribute> � ���� </TemplateAttribute> � ���� <Template> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "Object Group" /> ��������� <AttributeValue type= "TextString" value= "SASED-M-2-10-group" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute1" /> ��������� <AttributeValue type= "TextString" value= "CustomValue1" /> ��� ���� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute2" /> ��������� <AttributeValue type= "TextString" value= "CustomValue2" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "Name" /> ��������� <AttributeValue> � ���������� <NameValue type= "TextString" value= "SASED-M-2-10-template1" /> ����������� <NameType type= "Enumeration" ��������������������������� value= "UninterpretedTextString" /> ��������� </AttributeValue> � ���� �� </Attribute> � ���� </Template> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0080 0081 0082 0083 0084 0085 0086 0087 0088 0089 0090 0091 0092 0093 0094 0095 0096 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0097 0098 0099 0100 0101 0102 0103 0104 0105 0106 0107 0108 0109 0110 0111 0112 0113 0114 0115 0116 0117 0118 0119 0120 0121 0122 0123 0124 0125 0126 0127 0128 0129 0130 0131 0132 0133 0134 0135 0136 0137 0138 0139 0140 0141 # TIME 2 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <RequestPayload> � ���� <ObjectType type= "Enumeration" value= "SecretData" /> ����� <TemplateAttribute> � ������ <Name> � �������� <NameValue type= "TextString" value= "SASED-M-2-10-template1" /> ��������� <NameType type= "Enumeration" ����������������������������� value= "UninterpretedTextString" /> ������� </Name> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute3" /> ��������� <AttributeValue type= "TextString" value= "CustomValue3" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute4" /> ��������� <AttributeValue type= "TextString" value= "CustomValue4" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "Name" /> ��������� <AttributeValue> � ���������� <NameValue type= "TextString" value= "SASED-M-2-10-name" /> ����������� <NameType type= "Enumeration" ��������������������������� value= "UninterpretedTextString" /> ��������� </AttributeValue> � ������ </Attribute> � ���� </TemplateAttribute> � ���� <SecretData> � ������ <SecretDataType type= "Enumeration" value= "Password" /> ������� <KeyBlock> � �������� <KeyFormatType type= "Enumeration" value= "Opaque" /> ��������� <KeyValue> � ���������� <KeyMaterial type= "ByteString" ������������������������� value= "2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a" /> ��������� </KeyValue> � ������ </KeyBlock> � ���� </SecretData> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0142 0143 0144 0145 0146 0147 0148 0149 0150 0151 0152 0153 0154 0155 0156 0157 0158 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 3.1.3 SASED-M-3-10 - Retrieve Authentication Key Locate and retrieve the previously registered authentication key and finally destroy both the authentication key and the template. 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 0020 0021 0022 # TIME 0 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <RequestPayload> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Group" /> ������� <AttributeValue type= "TextString" value= "SASED-M-2-10-group" /> ����� </Attribute> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Type" /> ������� <AttributeValue type= "Enumeration" value= "SecretData" /> ����� </Attribute> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0023 0024 0025 0026 0027 0028 0029 0030 0031 0032 0033 0034 0035 0036 0037 0038 0039 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:13+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0040 0041 0042 0043 0044 0045 0046 0047 0048 0049 0050 0051 0052 0053 0054 0055 # TIME 1 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <AttributeName type= "TextString" value= "x-CustomAttribute4" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0056 0057 0058 0059 0060 0061 0062 0063 0064 0065 0066 0067 0068 0069 0070 0071 0072 0073 0074 0075 0076 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:14+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <Attribute> � ������ <AttributeName type= "TextString" value= "x-CustomAttribute4" /> ������� <AttributeValue type= "TextString" value= "CustomValue4" /> ����� </Attribute> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0077 0078 0079 0080 0081 0082 0083 0084 0085 0086 0087 0088 0089 0090 0091 0092 # TIME 2 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <AttributeName type= "TextString" value= "x-CustomAttribute3" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0093 0094 0095 0096 0097 0098 0099 0100 0101 0102 0103 0104 0105 0106 0107 0108 0109 0110 0111 0112 0113 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:14+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <Attribute> � ��� ��� <AttributeName type= "TextString" value= "x-CustomAttribute3" /> ������� <AttributeValue type= "TextString" value= "CustomValue3" /> ����� </Attribute> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0114 0115 0116 0117 0118 0119 0120 0121 0122 0123 0124 0125 0126 0127 0128 # TIME 3 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Get" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0129 0130 0131 0132 0133 0134 0135 0136 0137 0138 0139 0140 0141 0142 0143 0144 0145 0146 0147 0148 0149 0150 0151 0152 0153 0154 0155 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T17:01:41+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Get" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <ObjectType type= "Enumeration" value= "SecretData" /> ����� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <SecretData> � ������ <SecretDataType type= "Enumeration" value= "Password" /> ������� <KeyBlock> � �������� <KeyFormatType type= "Enumeration" value= "Opaque" /> ��������� <KeyValue> � ���������� <KeyMaterial type= "ByteString" ������������������������� value= "2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a" /> ��������� </KeyValue> � ������ </KeyBlock> � ���� </SecretData> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0156 0157 0158 0159 0160 0161 0162 0163 0164 0165 0166 0167 0168 0169 0170 # TIME 4 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> �� </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0171 0172 0173 0174 0175 0176 0177 0178 0179 0180 0181 0182 0183 0184 0185 0186 0187 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T17:01:41+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0188 0189 0190 0191 0192 0193 0194 0195 0196 0197 0198 0199 0200 0201 0202 0203 0204 0205 0206 0207 0208 0209 0210 0211 0212 # TIME 5 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <RequestPayload> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Name" /> ������� <AttributeValue> � �������� <NameValue type= "TextString" value= "SASED-M-2-10-template1" /> ��������� <NameType type= "Enumeration" ����������������������������� value= "UninterpretedTextString" /> ������� </AttributeValue> � ���� </Attribute> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Type" /> ������� <AttributeValue type= "Enumeration" value= "Template" /> ����� </Attribute> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0213 0214 0215 0216 0217 0218 0219 0220 0221 0222 0223 0224 0225 0226 0227 0228 0229 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0230 0231 0232 0233 0234 0235 0236 0237 0238 0239 0240 0241 0242 0243 0244 # TIME 6 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0245 0246 0247 0248 0249 0250 0251 0252 0253 0254 0255 0256 0257 0258 0259 0260 0261 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "0" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T17:01:41+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 3.2 Mandatory Test Cases KMIP v1.1 3.2.1 SASED-M-1-11 - Configuration Determine server configuration details including operations supported (only the mandatory operations are listed in the response example), objects supported (only the mandatory objects types are listed in the response example), and optional server information. 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0012 0013 0014 0015 0016 0017 # TIME 0 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Query" /> ��� <RequestPayload> � ���� <QueryFunction type= "Enumeration" value= "QueryOperations" /> ����� <QueryFunction type= "Enumeration" value= "QueryObjects" /> ���� � <QueryFunction type= "Enumeration" ���������������������������� value= "QueryServerInformation" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0018 0019 0020 0021 0022 0023 0024 0025 0026 0027 0028 0029 0030 0031 0032 0033 0034 0035 0036 0037 0038 0039 0040 0041 0042 0043 0044 0045 0046 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:03+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Query" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <Operation type= "Enumeration" value= "Query" /> ����� <Operation type= "Enumeration" value= "Locate" /> ����� <Operation type= "Enumeration" value= "Destroy" /> ����� <Operation type= "Enumeration" value= "Get" /> ����� <Operation type= "Enumeration" value= "Register" /> ����� <Operation type= "Enumeration" value= "GetAttributes" /> ����� <Operation type= "Enumeration" value= "GetAttributeList" /> ����� <Operation type= "Enumeration" value= "AddAttribute" /> ����� <ObjectType type= "Enumeration" value= "SecretData" /> ����� <ObjectType type= "Enumeration" value= "Template" /> ����� <VendorIdentification type= "TextString" value= "server-vendor.com" /> ����� <ServerInformation> � ���� </ServerInformation> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 3.2.2 SASED-M-2-11 - Register the authentication key A template is created and the secret data for the authentication key is then registered. The server must allow the registration of managed objects for Object Groups either by allowed arbitrary values for Object Groups or by pre-configuration of specific Object Groups prior to the storage array registering the authentication key.� The authentication key may be a new authentication key or a replacement authentication key. 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 0020 0021 0022 0023 0024 0025 # TIME 0 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <RequestPayload> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Name" /> ������� <AttributeValue> � ���� ���� <NameValue type= "TextString" value= "SASED-M-2-11-template1" /> ��������� <NameType type= "Enumeration" ����������������������������� value= "UninterpretedTextString" /> ������� </AttributeValue> � ���� </Attribute> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Type" /> ������� <AttributeValue type= "Enumeration" value= "Template" /> ����� </Attribute> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0026 0027 0028 0029 0030 0031 0032 0033 0034 0035 0036 0037 0038 0039 0040 0041 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0042 0043 0044 0045 0046 0047 0048 0049 0050 0051 0052 0053 0054 0055 0056 0057 0058 0059 0060 0061 0062 0063 0064 0065 0066 0067 0068 0069 0070 0071 0072 0073 0074 0075 0076 0077 0078 0079 # TIME 1 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <RequestPayload> � ���� <ObjectType type= "Enumeration" value= "Template" /> ����� <TemplateAttribute> � ���� </TemplateAttribute> � ���� <Template> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "Object Group" /> � �������� <AttributeValue type= "TextString" value= "SASED-M-2-11-group" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute1" /> ��������� <AttributeValue type= "TextString" value= "CustomValue1" /> ���� ��� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute2" /> ��������� <AttributeValue type= "TextString" value= "CustomValue2" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "Name" /> ��������� <AttributeValue> � ���������� <NameValue type= "TextString" value= "SASED-M-2-11-template1" /> ����������� <NameType type= "Enumeration" ��������������������������� value= "UninterpretedTextString" /> ��������� </AttributeValue> � ����� � </Attribute> � ���� </Template> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0080 0081 0082 0083 0084 0085 0086 0087 0088 0089 0090 0091 0092 0093 0094 0095 0096 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0097 0098 0099 0100 0101 0102 0103 0104 0105 0106 0107 0108 0109 0110 0111 0112 0113 0114 0115 0116 0117 0118 0119 0120 0121 0122 0123 0124 0125 0126 0127 0128 0129 0130 0131 0132 0133 0134 0135 0136 0137 0138 0139 0140 0141 # TIME 2 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <RequestPayload> � ���� <ObjectType type= "Enumeration" value= "SecretData" /> ����� <TemplateAttribute> � ������ <Name> � �������� <NameValue type= "TextString" value= "SASED-M-2-11-template1" /> ��������� <NameType type= "Enumeration" ����������������������������� value= "UninterpretedTextString" /> ������� </Name> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute3" /> ��������� <AttributeValue type= "TextString" value= "CustomValue3" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute4" /> ��������� <AttributeValue type= "TextString" value= "CustomValue4" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "Name" /> ��������� <AttributeValue> � ���������� <NameValue type= "TextString" value= "SASED-M-2-11-name" /> ����������� <NameType type= "Enumeration" ��������������������������� value= "UninterpretedTextString" /> ��������� </AttributeValue> � ������ </Attribute> � ���� </TemplateAttribute> � ���� <SecretData> � ������ <SecretDataType type= "Enumeration" value= "Password" /> ������� <KeyBlock> � �������� <KeyFormatType type= "Enumeration" value= "Opaque" /> ��������� <KeyValue> � ���������� <KeyMaterial type= "ByteString" ������������������������� value= "2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a" /> ��������� </KeyValue> � ������ </KeyBlock> � ���� </SecretData> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0142 0143 0144 0145 0146 0147 0148 0149 0150 0151 0152 0153 0154 0155 0156 0157 0158 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 3.2.3 SASED-M-3-11 - Retrieve Authentication Key Locate and retrieve the previously registered authentication key and finally destroy both the authentication key and the template. 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 0020 0021 0022 # TIME 0 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <RequestPayload> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Group" /> ������� <AttributeValue type= "TextString" value= "SASED-M-2-11-group" /> ����� </Attribute> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Type" /> ������� <AttributeValue type= "Enumeration" value= "SecretData" /> ����� </Attribute> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0023 0024 0025 0026 0027 0028 0029 0030 0031 0032 0033 0034 0035 0036 0037 0038 0039 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:13+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0040 0041 0042 0043 0044 0045 0046 0047 0048 0049 0050 0051 0052 0053 0054 0055 # TIME 1 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <AttributeName type= "TextString" value= "x-CustomAttribute4" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0056 0057 0058 0059 0060 0061 0062 0063 0064 0065 0066 0067 0068 0069 0070 0071 0072 0073 0074 0075 0076 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:14+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <Attribute> � ������ <AttributeName type= "TextString" value= "x-CustomAttribute4" /> ������� <AttributeValue type= "TextString" value= "CustomValue4" /> ����� </Attribute> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0077 0078 0079 0080 0081 0082 0083 0084 0085 0086 0087 0088 0089 0090 0091 0092 # TIME 2 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <AttributeName type= "TextString" value= "x-CustomAttribute3" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0093 0094 0095 0096 0097 0098 0099 0100 0101 0102 0103 0104 0105 0106 0107 0108 0109 0110 0111 0112 0113 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:14+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <Attribute> � ���� �� <AttributeName type= "TextString" value= "x-CustomAttribute3" /> ������� <AttributeValue type= "TextString" value= "CustomValue3" /> ����� </Attribute> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0114 0115 0116 0117 0118 0119 0120 0121 0122 0123 0124 0125 0126 0127 0128 # TIME 3 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Get" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0129 0130 0131 0132 0133 0134 0135 0136 0137 0138 0139 0140 0141 0142 0143 0144 0145 0146 0147 0148 0149 0150 0151 0152 0153 0154 0155 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T17:01:41+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Get" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <ObjectType type= "Enumeration" value= "SecretData" /> ����� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <SecretData> � ������ <SecretDataType type= "Enumeration" value= "Password" /> ������� <KeyBlock> � �������� <KeyFormatType type= "Enumeration" value= "Opaque" /> ��������� <KeyValue> � ���������� <KeyMaterial type= "ByteString" ������������������������� value= "2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a" /> ��������� </KeyValue> � ������ </KeyBlock> � ���� </SecretData> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0156 0157 0158 0159 0160 0161 0162 0163 0164 0165 0166 0167 0168 0169 0170 # TIME 4 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0171 0172 0173 0174 0175 0176 0177 0178 0179 0180 0181 0182 0183 0184 0185 0186 0187 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T17:01:41+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0188 0189 0190 0191 0192 0193 0194 0195 0196 0197 0198 0199 0200 0201 0202 0203 0204 0205 0206 0207 0208 0209 0210 0211 0212 # TIME 5 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <RequestPayload> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Name" /> ������� <AttributeValue> � �������� <NameValue type= "TextString" value= "SASED-M-2-11-template1" /> ��������� <NameType type= "Enumeration" ����������������������������� value= "UninterpretedTextString" /> ������� </AttributeValue> � ���� </Attribute> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Type" /> ������� <AttributeValue type= "Enumeration" value= "Template" /> ����� </Attribute> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0213 0214 0215 0216 0217 0218 0219 0220 0221 0222 0223 0224 0225 0226 0227 0228 0229 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0230 0231 0232 0233 0234 0235 0236 0237 0238 0239 0240 0241 0242 0243 0244 # TIME 6 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0245 0246 0247 0248 0249 0250 0251 0252 0253 0254 0255 0256 0257 0258 0259 0260 0261 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "1" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T17:01:41+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 3.3 Mandatory Test Cases KMIP v1.2 3.3.1 SASED-M-1-12 - Configuration Determine server configuration details including operations supported (only the mandatory operations are listed in the response example), objects supported (only the mandatory objects types are listed in the response example), and optional server information. 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0012 0013 0014 0015 0016 0017 # TIME 0 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Query" /> ��� <RequestPayload> � ���� <QueryFunction type= "Enumeration" value= "QueryOperations" /> ����� <QueryFunction type= "Enumeration" value= "QueryObjects" /> ����� <QueryFunction type= "Enumeration" ���������������������������� value= "QueryServerInformation" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0018 0019 0020 0021 0022 0023 0024 0025 0026 0027 0028 0029 0030 0031 0032 0033 0034 0035 0036 0037 0038 0039 0040 0041 0042 0043 0044 0045 0046 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:03+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Query" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <Operation type= "Enumeration" value= "Query" /> ����� <Operation type= "Enumeration" value= "Locate" /> ����� <Operation type= "Enumeration" value= "Destroy" /> ����� <Operation type= "Enumeration" value= "Get" /> ����� <Operation type= "Enumeration" value= "Register" /> ����� <Operation type= "Enumeration" value= "GetAttributes" /> ����� <Operation type= "Enumeration" value= "GetAttributeList" /> ����� <Operation type= "Enumeration" value= "AddAttribute" /> ����� <ObjectType type= "Enumeration" value= "SecretData" /> ����� <ObjectType type= "Enumeration" value= "Template" /> ����� <VendorIdentification type= "TextString" value= "server-vendor.com" /> ����� <ServerInformation> � ���� </ServerInformation> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 3.3.2 SASED-M-2-12 - Register the authentication key A template is created and the secret data for the authentication key is then registered. The server must allow the registration of managed objects for Object Groups either by allowed arbitrary values for Object Groups or by pre-configuration of specific Object Groups prior to the storage array registering the authentication key.� The authentication key may be a new authentication key or a replacement authentication key. 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 0020 0021 0022 0023 0024 0025 # TIME 0 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <RequestPayload> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Name" /> ������� <AttributeValue> � ������ �� <NameValue type= "TextString" value= "SASED-M-2-12-template1" /> ��������� <NameType type= "Enumeration" ����������������������������� value= "UninterpretedTextString" /> ������� </AttributeValue> � ���� </Attribute> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Type" /> ������� <AttributeValue type= "Enumeration" value= "Template" /> ����� </Attribute> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0026 0027 0028 0029 0030 0031 0032 0033 0034 0035 0036 0037 0038 0039 0040 0041 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0042 0043 0044 0045 0046 0047 0048 0049 0050 0051 0052 0053 0054 0055 0056 0057 0058 0059 0060 0061 0062 0063 0064 0065 0066 0067 0068 0069 0070 0071 0072 0073 0074 0075 0076 0077 0078 0079 # TIME 1 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <RequestPayload> � ���� <ObjectType type= "Enumeration" value= "Template" /> ����� <TemplateAttribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "Name" /> ��������� <AttributeValue> � ���������� <NameValue type= "TextString" value= "SASED-M-2-12-template1" /> ����������� <NameType type= "Enumeration" ��������������������������� value= "UninterpretedTextString" /> ��������� </AttributeValue> � ������ </Attribute> � ���� </TemplateAttribute> � ���� <Template> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "Object Group" /> ��������� <AttributeValue type= "TextString" value= "SASED-M-2-12-group" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute1" /> ��������� <AttributeValue type= "TextString" value= "CustomValue1" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute2" /> ��������� <AttributeValue type= "TextString" value= "CustomValue2" /> ������� </Attribute> � ���� </Template> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0080 0081 0082 0083 0084 0085 0086 0087 0088 0089 0090 0091 0092 0093 0094 0095 0096 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0097 0098 0099 0100 0101 0102 0103 0104 0105 0106 0107 0108 0109 0110 0111 0112 0113 0114 0115 0116 0117 0118 0119 0120 0121 0122 0123 0124 0125 0126 0127 0128 0129 0130 0131 0132 0133 0134 0135 0136 0137 0138 0139 0140 0141 # TIME 2 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <RequestPayload> � ���� <ObjectType type= "Enumeration" value= "SecretData" /> ����� <TemplateAttribute> � ������ <Name> � �������� <NameValue type= "TextString" value= "SASED-M-2-12-template1" /> ��������� <NameType type= "Enumeration" ����������������������������� value= "UninterpretedTextString" /> ������� </Name> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute3" /> ��������� <AttributeValue type= "TextString" value= "CustomValue3" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "x-CustomAttribute4" /> ��������� <AttributeValue type= "TextString" value= "CustomValue4" /> ������� </Attribute> � ������ <Attribute> � �������� <AttributeName type= "TextString" value= "Name" /> ��������� <AttributeValue> � ���������� <NameValue type= "TextString" value= "SASED-M-2-12-name" /> ����������� <NameType type= "Enumeration" ��������������������������� value= "UninterpretedTextString" /> � �������� </AttributeValue> � ������ </Attribute> � ���� </TemplateAttribute> � ���� <SecretData> � ������ <SecretDataType type= "Enumeration" value= "Password" /> ������� <KeyBlock> � �������� <KeyFormatType type= "Enumeration" value= "Opaque" /> ��������� <KeyValue> � ���������� <KeyMaterial type= "ByteString" ������������������������� value= "2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a" /> ��������� </KeyValue> � ������ </KeyBlock> � ���� </SecretData> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0142 0143 0144 0145 0146 0147 0148 0149 0150 0151 0152 0153 0154 0155 0156 0157 0158 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Register" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 3.3.3 SASED-M-3-12 - Retrieve Authentication Key Locate and retrieve the previously registered authentication key and finally destroy both the authentication key and the template. 0001 0002 0003 0004 0005 0006 0007 0008 0009 0010 0011 0012 0013 0014 0015 0016 0017 0018 0019 0020 0021 0022 # TIME 0 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � � � <Operation type= "Enumeration" value= "Locate" /> ��� <RequestPayload> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Group" /> ������� <AttributeValue type= "TextString" value= "SASED-M-2-12-group" /> ����� </Attribute> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Type" /> ������� <AttributeValue type= "Enumeration" value= "SecretData" /> ����� </Attribute> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0023 0024 0025 0026 0027 0028 0029 0030 0031 0032 0033 0034 0035 0036 0037 0038 0039 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:13+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0040 0041 0042 0043 0044 0045 0046 0047 0048 0049 0050 0051 0052 0053 0054 0055 # TIME 1 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <AttributeName type= "TextString" value= "x-CustomAttribute4" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0056 0057 0058 0059 0060 0061 0062 0063 0064 0065 0066 0067 0068 0069 0070 0071 0072 0073 0074 0075 0076 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:14+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <Attribute> � ������ <AttributeName type= "TextString" value= "x-CustomAttribute4" /> ������� <AttributeValue type= "TextString" value= "CustomValue4" /> ����� </Attribute> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0077 0078 0079 0080 0081 0082 0083 0084 0085 0086 0087 0088 0089 0090 0091 0092 # TIME 2 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <AttributeName type= "TextString" value= "x-CustomAttribute3" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0093 0094 0095 0096 0097 0098 0099 0100 0101 0102 0103 0104 0105 0106 0107 0108 0109 0110 0111 0112 0113 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:14+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "GetAttributes" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <Attribute> � ������ <AttributeName type= "TextString" value= "x-CustomAttribute3" /> ������� <AttributeValue type= "TextString" value= "CustomValue3" /> ����� </Attribute> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0114 0115 0116 0117 0118 0119 0120 0121 0122 0123 0124 0125 0126 0127 0128 # TIME 3 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Get" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0129 0130 0131 0132 0133 0134 0135 0136 0137 0138 0139 0140 0141 0142 0143 0144 0145 0146 0147 0148 0149 0150 0151 0152 0153 0154 0155 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T17:01:41+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Get" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <ObjectType type= "Enumeration" value= "SecretData" /> ����� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ����� <SecretData> � ������ <SecretDataType type= "Enumeration" value= "Password" /> ������� <KeyBlock> � �������� <KeyFormatType type= "Enumeration" value= "Opaque" /> ��������� <KeyValue> � ���������� <KeyMaterial type= "ByteString" ������������������������� value= "2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a2a" /> ��������� </KeyValue> � ������ </KeyBlock> � ���� </SecretData> � �� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0156 0157 0158 0159 0160 0161 0162 0163 0164 0165 0166 0167 0168 0169 0170 # TIME 4 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0171 0172 0173 0174 0175 0176 0177 0178 0179 0180 0181 0182 0183 0184 0185 0186 0187 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T17:01:41+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_0" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0188 0189 0190 0191 0192 0193 0194 0195 0196 0197 0198 0199 0200 0201 0202 0203 0204 0205 0206 0207 0208 0209 0210 0211 0212 # TIME 5 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <RequestPayload> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Name" /> ������� <AttributeValue> � �������� <NameValue type= "TextString" value= "SASED-M-2-12-template1" /> ��������� <NameType type= "Enumeration" ����������������������������� value= "UninterpretedTextString" /> ������� </AttributeValue> � ���� </Attribute> � ���� <Attribute> � ������ <AttributeName type= "TextString" value= "Object Type" /> ������� <AttributeValue type= "Enumeration" value= "Template" /> ����� </Attribute> � �� </RequestPayload> � � </BatchItem> </RequestMessage> 0213 0214 0215 0216 0217 0218 0219 0220 0221 0222 0223 0224 0225 0226 0227 0228 0229 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T16:53:08+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Locate" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 0230 0231 0232 0233 0234 0235 0236 0237 0238 0239 0240 0241 0242 0243 0244 # TIME 6 <RequestMessage> � � <RequestHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <BatchCount type= "Integer" value= "1" /> � </RequestHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <RequestPayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </RequestPayload> � � </BatchItem> </RequestMessage> 0245 0246 0247 0248 0249 0250 0251 0252 0253 0254 0255 0256 0257 0258 0259 0260 0261 <ResponseMessage> � � <ResponseHeader> � �� <ProtocolVersion> � ���� <ProtocolVersionMajor type= "Integer" value= "1" /> ����� <ProtocolVersionMinor type= "Integer" value= "2" /> ��� </ProtocolVersion> � �� <TimeStamp type= "DateTime" value= "2013-04-25T17:01:41+00:00" /> ��� <BatchCount type= "Integer" value= "1" /> � </ResponseHeader> � � <BatchItem> � �� <Operation type= "Enumeration" value= "Destroy" /> ��� <ResultStatus type= "Enumeration" value= "Success" /> ��� <ResponsePayload> � ���� <UniqueIdentifier type= "TextString" �������������������������� value= "$UNIQUE_IDENTIFIER_1" /> ��� </ResponsePayload> � � </BatchItem> </ResponseMessage> 4 Conformance 4.1 Storage Array with Self Encrypting Drive Client KMIP v1.0 Profile Conformance KMIP client implementations conformant to this profile: SHALL support the Authentication Suite conditions ( 2.1) SHALL support the Storage Array with Self-Encrypting Drives - Client conditions (2.2) SHALL support all the Mandatory Test Cases KMIP v1.0 (3.1) 4.2 Storage Array with Self Encrypting Drive Client KMIP v1.1 Profile Conformance KMIP client implementations conformant to this profile: SHALL support the Authentication Suite conditions ( 2.1) SHALL support the Storage Array with Self-Encrypting Drives - Client conditions (2.2) SHALL support all the Mandatory Test Cases KMIP v1.1 (3.2) 4.3 Storage Array with Self Encrypting Drive Client KMIP v1.2 Profile Conformance KMIP client implementations conformant to this profile: SHALL support the Authentication Suite conditions ( 2.1) SHALL support the Storage Array with Self-Encrypting Drives - Client conditions (2.2) SHALL support all the Mandatory Test Cases KMIP v1.2 (3.3) 4.4 Storage Array with Self Encrypting Drive Server KMIP v1.0 Profile Conformance KMIP server implementations conformant to this profile: SHALL support the Authentication Suite conditions ( 2.1) SHALL support the Storage Array with Self-Encrypting Drives - Server conditions (2.3) SHALL support all the Mandatory Test Cases KMIP v1.0 (3.1) 4.5 Storage Array with Self Encrypting Drive Server KMIP v1.1 Profile Conformance KMIP server implementations conformant to this profile: SHALL support the Authentication Suite conditions ( 2.1) SHALL support the Storage Array with Self-Encrypting Drives - Server conditions (2.3) SHALL support all the Mandatory Test Cases KMIP v1.1 (3.2) 4.6 Storage Array with Self Encrypting Drive Server KMIP v1.2 Profile Conformance KMIP server implementations conformant to this profile: SHALL support the Authentication Suite conditions ( 2.1) SHALL support the Storage Array with Self-Encrypting Drives - Server conditions (2.3) SHALL support all the Mandatory Test Cases KMIP v1.2 (3.3) 4.7 Permitted Test Case Variations Whilst the test cases provided in this Profile define the allowed request and response content, some inherent variations MAY occur and are permitted within a successfully completed test case. Each test case MAY include allowed variations in the description of the test case in addition to the variations noted in this section. Other variations not explicitly noted in this Profile SHALL be deemed non-conformant. 4.7.1 Variable Items An implementation conformant to this Profile MAY vary the following values: UniqueIdentifier PrivateKeyUniqueIdentifier PublicKeyUniqueIdentifier UniqueBatchItemIdentifier AsynchronousCorrelationValue TimeStamp KeyValue / KeyMaterial including: key material content returned for managed cryptographic objects which are generated by the server wrapped versions of keys where the wrapping key is dynamic or the wrapping contains variable output for each wrap operation For response containing the output of cryptographic operation in Data / SignatureData/ MACData / IVCounterNonce where: the managed object is generated by the server; or the operation inherently contains variable output For the following DateTime attributes where the value is not specified in the request as a fixed DateTime value: ActivationDate ArchiveDate CompromiseDate CompromiseOccurrenceDate DeactivationDate DestroyDate InitialDate LastChangeDate ProtectStartDate ProcessStopDate ValidityDate OriginalCreationDate LinkedObjectIdentifier DigestValue For those managed cryptographic objects which are dynamically generated KeyFormatType The key format type selected by the server when it creates managed objects Digest a. The HashingAlgorithm selected by the server when it calculates the digest for a managed object for which it has access to the key material b. The Digest Value Extensions reported in Query for ExtensionList and ExtensionMap Application Namespaces reported in Query Object Types reported in Query other than those noted as required in this profile Operation Types reported in Query other than those noted as required in this profile (or any referenced profile documents) For TextString attribute values containing test identifiers: a. �Additional vendor or application prefixes Additional attributes beyond those noted in the response ���������������������������������������������������������������������������������������� An implementation conformant to this Profile MAY allow the following response variations: Object Group values � May or may not return one or more Object Group values not included in the requests y-CustomAttributes � May or may not include additional server-specific associated attributes not included in requests Message Extensions � May or may not include additional (non-critical) vendor extensions TemplateAttribute � May or may not be included in responses where the Template Attribute response is noted as optional in [KMIP-SPEC] AttributeIndex � May or may not include Attribute Index value where the Attribute Index value is 0 for Protocol Versions 1.1 and above. ResultMessage � May or may not be included in responses and the value (if included) may vary from the text contained within the test case. The list of Protocol Versions returned in a DiscoverVersion response may include additional protocol versions if the request has not specified a list of client supported Protocol Versions. VendorIdentification - The value (if included) may vary from the text contained within the test case. 4.7.2 Variable behavior An implementation conformant to this Profile SHALL allow variation of the following behavior: A test MAY omit the clean-up requests and responses (containing Revoke and/or Destroy) at the end of the test provided there is a separate mechanism to remove the created objects during testing. A test MAY omit the test identifiers if the client is unable to include them in requests. This includes the following attributes: Name; and x-ID A test MAY perform requests with multiple batch items or as multiple requests with a single batch item provided the sequence of operations are equivalent A request MAY contain an optional Authentication [KMIP_SPEC] structure within each request Appendix A. Acknowledgments The following individuals have participated in the creation of this specification and are gratefully acknowledged: Participants: Hal Aldridge, Sypris Electronics Mike Allen, Symantec Gordon Arnold, IBM Todd Arnold, IBM Richard Austin, Hewlett-Packard Lars Bagnert, PrimeKey Elaine Barker, NIST Peter Bartok, Venafi, Inc. Tom Benjamin, IBM Anthony Berglas, Cryptsoft Mathias Bj�rkqvist, IBM Kevin Bocket, Venafi Anne Bolgert, IBM Alan Brown, Thales e-Security Tim Bruce, CA Technologies Chris Burchett, Credant Technologies, Inc. Kelley Burgin, National Security Agency Robert Burns, Thales e-Security Chuck Castleton, Venafi Kenli Chong, QuintessenceLabs John Clark, Hewlett-Packard Tom Clifford, Symantec Corp. Doron Cohen, SafeNet, Inc Tony Cox, Cryptsoft Russell Dietz, SafeNet, Inc Graydon Dodson, Lexmark International Inc. Vinod Duggirala, EMC Corporation Chris Dunn, SafeNet, Inc. Michael Duren, Sypris Electronics James Dzierzanowski, American Express CCoE Faisal Faruqui, Thales e-Security Stan Feather, Hewlett-Packard David Finkelstein, Symantec Corp. James Fitzgerald, SafeNet, Inc. Indra Fitzgerald, Hewlett-Packard Judith Furlong, EMC Corporation Susan Gleeson, Oracle Robert Griffin, EMC Corporation Paul Grojean, Individual Robert Haas, IBM Thomas Hardjono, M.I.T. ChengDong He, Huawei Technologies Co., Ltd. Steve He, Vormetric Kurt Heberlein, Hewlett-Packard Larry Hofer, Emulex Corporation Maryann Hondo, IBM Walt Hubis, NetApp Tim Hudson, Cryptsoft Jonas Iggbom, Venafi, Inc. Sitaram Inguva, American Express CCoE Jay Jacobs, Target Corporation Glen Jaquette, IBM Mahadev Karadiguddi, NetApp Greg Kazmierczak, Wave Systems Corp. Marc Kenig, SafeNet, Inc. Mark Knight, Thales e-Security Kathy Kriese, Symantec Corporation Mark Lambiase, SecureAuth John Leiseboer, Quintenssence Labs Hal Lockhart, Oracle Corporation Robert Lockhart, Thales e-Security Anne Luk, Cryptsoft Sairam Manidi, Freescale Luther Martin, Voltage Security Neil McEvoy, iFOSSF Marina Milshtein, Individual Dale Moberg, Axway Software Jishnu Mukeri, Hewlett-Packard Bryan Olson, Hewlett-Packard John Peck, IBM Rob Philpott, EMC Corporation Denis Pochuev, SafeNet, Inc. Reid Poole, Venafi, Inc. Ajai Puri, SafeNet, Inc. Saravanan Ramalingam, Thales e-Security Peter Reed, SafeNet, Inc. Bruce Rich, IBM Christina Richards, American Express CCoE Warren Robbins, Dell Peter Robinson, EMC Corporation Scott Rotondo, Oracle Saikat Saha, SafeNet, Inc. Anil Saldhana, Red Hat Subhash Sankuratripati, NetApp Boris Schumperli, Cryptomathic Greg Singh, QuintessenceLabs David Smith, Venafi, Inc Brian Spector, Certivox Terence Spies, Voltage Security Deborah Steckroth, RouteOne LLC Michael Stevens, QuintessenceLabs Marcus Streets, Thales e-Security Satish Sundar, IBM Kiran Thota, VMware Somanchi Trinath, Freescale Semiconductor, Inc. Nathan Turajski, Thales e-Security Sean Turner, IECA, Inc. Paul Turner, Venafi, Inc. Rod Wideman, Quantum Corporation Steven Wierenga, Hewlett-Packard Jin Wong, QuintessenceLabs Sameer Yami, Thales e-Security Peter Yee, EMC Corporation Krishna Yellepeddy, IBM Catherine Ying, SafeNet, Inc. Tatu Ylonen, SSH Communications Security (Tectia Corp) Michael Yoder, Vormetric. Inc. Magda Zdunkiewicz, Cryptsoft Peter Zelechoski, Election Systems & Software Appendix B. KMIP Specification Cross Reference Reference Term KMIP 1.0 KMIP 1.1 KMIP 1.2 1 Introduction Non-Normative References 1.3. 1.3. 1.3. Normative References 1.2. 1.2. 1.2. Terminology 1.1. 1.1. 1.1. 2 Objects Attribute 2.1.1. 2.1.1. 2.1.1. Base Objects 2.1. 2.1. 2.1. Certificate 2.2.1. 2.2.1. 2.2.1. Credential 2.1.2. 2.1.2. 2.1.2. Data - - 2.1.10. Data Length - - 2.1.11. Extension Information - 2.1.9. 2.1.9. Key Block 2.1.3. 2.1.3. 2.1.3. Key Value 2.1.4. 2.1.4. 2.1.4. Key Wrapping Data 2.1.5. 2.1.5. 2.1.5. Key Wrapping Specification 2.1.6. 2.1.6. 2.1.6. MAC Data - - 2.1.13. Managed Objects 2.2. 2.2. 2.2. Nonce - - 2.1.14. Opaque Object 2.2.8. 2.2.8. 2.2.8. PGP Key - - 2.2.9. Private Key 2.2.4. 2.2.4. 2.2.4. Public Key 2.2.3. 2.2.3. 2.2.3. Secret Data 2.2.7. 2.2.7. 2.2.7. Signature Data - - 2.1.12. Split Key 2.2.5. 2.2.5. 2.2.5. Symmetric Key 2.2.2. 2.2.2. 2.2.2. Template 2.2.6. 2.2.6. 2.2.6. Template-Attribute Structures 2.1.8. 2.1.8. 2.1.8. Transparent DH Private Key 2.1.7.6. 2.1.7.6. 2.1.7.6. Transparent DH Public Key 2.1.7.7. 2.1.7.7. 2.1.7.7. Transparent DSA Private Key 2.1.7.2. 2.1.7.2. 2.1.7.2. Transparent DSA Public Key 2.1.7.3. 2.1.7.3. 2.1.7.3. Transparent ECDH Private Key 2.1.7.10. 2.1.7.10. 2.1.7.10. Transparent ECDH Public Key 2.1.7.11. 2.1.7.11. 2.1.7.11. Transparent ECDSA Private Key 2.1.7.8. 2.1.7.8. 2.1.7.8. Transparent ECDSA Public Key 2.1.7.9. 2.1.7.9. 2.1.7.9. Transparent ECMQV Private Key 2.1.7.12. 2.1.7.12. 2.1.7.12. Transparent ECMQV Public Key 2.1.7.13. 2.1.7.13. 2.1.7.13. Transparent Key Structures 2.1.7. 2.1.7. 2.1.7. Transparent RSA Private Key 2.1.7.4. 2.1.7.4. 2.1.7.4. Transparent RSA Public Key 2.1.7.5. 2.1.7.5. 2.1.7.5. Transparent Symmetric Key 2.1.7.1. 2.1.7.1. 2.1.7.1. 3 Attributes Activation Date 3.19. 3.24. 3.24. Alternative Name - - 3.40. Application Specific Information 3.30. 3.36. 3.36. Archive Date 3.27. 3.32. 3.32. Attributes 3 3 3 Certificate Identifier 3.9. 3.13. 3.13. Certificate Issuer 3.11. 3.15. 3.15. Certificate Length - 3.9. 3.9. Certificate Subject 3.10. 3.14. 3.14. Certificate Type 3.8. 3.8. 3.8. Compromise Date 3.25. 3.30. 3.30. Compromise Occurrence Date 3.24. 3.29. 3.29. Contact Information 3.31. 3.37. 3.37. Cryptographic Algorithm 3.4. 3.4. 3.4. Cryptographic Domain Parameters 3.7. 3.7. 3.7. Cryptographic Length 3.5. 3.5. 3.5. Cryptographic Parameters 3.6. 3.6. 3.6. Custom Attribute 3.33. 3.39. 3.39. Deactivation Date 3.22. 3.27. 3.27. Default Operation Policy 3.13.2. 3.18.2. 3.18.2. Default Operation Policy for Certificates and Public Key Objects 3.13.2.2. 3.18.2.2. 3.18.2.2. Default Operation Policy for Secret Objects 3.13.2.1. 3.18.2.1. 3.18.2.1. Default Operation Policy for Template Objects 3.13.2.3. 3.18.2.3. 3.18.2.3. Destroy Date 3.23. 3.28. 3.28. Digest 3.12. 3.17. 3.17. Digital Signature Algorithm - 3.16. 3.16. Fresh - 3.34. 3.34. Initial Date 3.18. 3.23. 3.23. Key Value Location - - 3.42. Key Value Present - - 3.41. Last Change Date 3.32. 3.38. 3.38. Lease Time 3.15. 3.20. 3.20. Link 3.29. 3.35. 3.35. Name 3.2. 3.2. 3.2. Object Group 3.28. 3.33. 3.33. Object Type 3.3. 3.3. 3.3. Operation Policy Name 3.13. 3.18. 3.18. Operations outside of operation policy control 3.13.1. 3.18.1. 3.18.1. Original Creation Date - - 3.43. Process Start Date 3.20. 3.25. 3.25. Protect Stop Date 3.21. 3.26. 3.26. Revocation Reason 3.26. 3.31. 3.31. State 3.17. 3.22. 3.22. Unique Identifier 3.1. 3.1. 3.1. Usage Limits 3.16. 3.21. 3.21. X.509 Certificate Identifier - 3.10. 3.10. X.509 Certificate Issuer - 3.12. 3.12. X.509 Certificate Subject - 3.11. 3.11. 4 Client-to-Server Operations Activate 4.18. 4.19. 4.19. Add Attribute 4.13. 4.14. 4.14. Archive 4.21. 4.22. 4.22. Cancel 4.25. 4.27. 4.27. Certify 4.6. 4.7. 4.7. Check 4.9. 4.10. 4.10. Create 4.1. 4.1. 4.1. Create Key Pair 4.2. 4.2. 4.2. Create Split Key - - 4.38. Decrypt - - 4.30. Delete Attribute 4.15. 4.16. 4.16. Derive Key 4.5. 4.6. 4.6. Destroy 4.20. 4.21. 4.21. Discover Versions - 4.26. 4.26. Encrypt - - 4.29. Get 4.10. 4.11. 4.11. Get Attribute List 4.12. 4.13. 4.13. Get Attributes 4.11. 4.12. 4.12. Get Usage Allocation 4.17. 4.18. 4.18. Hash - - 4.37. Join Split Key - - 4.39. Locate 4.8. 4.9. 4.9. MAC - - 4.33. MAC Verify - - 4.34. Modify Attribute 4.14. 4.15. 4.15. Obtain Lease 4.16. 4.17. 4.17. Poll 4.26. 4.28. 4.28. Query 4.24. 4.25. 4.25. Re-certify 4.7. 4.8. 4.8. Recover 4.22. 4.23. 4.23. Register 4.3. 4.3. 4.3. Re-key 4.4. 4.4. 4.4. Re-key Key Pair - 4.5. 4.5. Revoke 4.19. 4.20. 4.20. RNG Retrieve - - 4.35. RNG Seed - - 4.36. Sign - - 4.31. Signature Verify - - 4.32. Validate 4.23. 4.24. 4.24. 5 Server-to-Client Operations Notify 5.1. 5.1. 5.1. Put 5.2. 5.2. 5.2. 6 Message Contents Asynchronous Correlation Value 6.8. 6.8. 6.8. Asynchronous Indicator 6.7. 6.7. 6.7. Attestation Capable Indicator - - 6.17. Batch Count 6.14. 6.14. 6.14. Batch Error Continuation Option 6.13. 6.13. 6.13. Batch Item 6.15. 6.15. 6.15. Batch Order Option 6.12. 6.12. 6.12. Maximum Response Size 6.3. 6.3. 6.3. Message Extension 6.16. 6.16. 6.16. Operation 6.2. 6.2. 6.2. Protocol Version 6.1. 6.1. 6.1. Result Message 6.11. 6.11. 6.11. Result Reason 6.10. 6.10. 6.10. Result Status 6.9. 6.9. 6.9. Time Stamp 6.5. 6.5. 6.5. Unique Batch Item ID 6.4. 6.4. 6.4. 7 Message Format Message Structure 7.1. 7.1. 7.1. Operations 7.2. 7.2. 7.2. 8 Authentication Authentication 8 8 8 9 Message Encoding Alternative Name Type Enumeration - - 9.1.3.2.34. Attestation Type Enumeration - - 9.1.3.2.36. Batch Error Continuation Option Enumeration 9.1.3.2.29. 9.1.3.2.30. 9.1.3.2.30. Bit Masks 9.1.3.3. 9.1.3.3. 9.1.3.3. Block Cipher Mode Enumeration 9.1.3.2.13. 9.1.3.2.14. 9.1.3.2.14. Cancellation Result Enumeration 9.1.3.2.24. 9.1.3.2.25. 9.1.3.2.25. Certificate Request Type Enumeration 9.1.3.2.21. 9.1.3.2.22. 9.1.3.2.22. Certificate Type Enumeration 9.1.3.2.6. 9.1.3.2.6. 9.1.3.2.6. Credential Type Enumeration 9.1.3.2.1. 9.1.3.2.1. 9.1.3.2.1. Cryptographic Algorithm Enumeration 9.1.3.2.12. 9.1.3.2.13. 9.1.3.2.13. Cryptographic Usage Mask 9.1.3.3.1. 9.1.3.3.1. 9.1.3.3.1. Defined Values 9.1.3. 9.1.3. 9.1.3. Derivation Method Enumeration 9.1.3.2.20. 9.1.3.2.21. 9.1.3.2.21. Digital Signature Algorithm Enumeration - 9.1.3.2.7. 9.1.3.2.7. Encoding Option Enumeration - 9.1.3.2.32. 9.1.3.2.32. Enumerations 9.1.3.2. 9.1.3.2. 9.1.3.2. Examples 9.1.2. 9.1.2. 9.1.2. Hashing Algorithm Enumeration 9.1.3.2.15. 9.1.3.2.16. 9.1.3.2.16. Item Length 9.1.1.3. 9.1.1.3. 9.1.1.3. Item Tag 9.1.1.1. 9.1.1.1. 9.1.1.1. Item Type 9.1.1.2. 9.1.1.2. 9.1.1.2. Item Value 9.1.1.4. 9.1.1.4. 9.1.1.4. Key Compression Type Enumeration 9.1.3.2.2. 9.1.3.2.2. 9.1.3.2.2. Key Format Type Enumeration 9.1.3.2.3. 9.1.3.2.3. 9.1.3.2.3. Key Role Type Enumeration 9.1.3.2.16. 9.1.3.2.17. 9.1.3.2.17. Key Value Location Type Enumeration - - 9.1.3.2.35. Link Type Enumeration 9.1.3.2.19. 9.1.3.2.20. 9.1.3.2.20. Name Type Enumeration 9.1.3.2.10. 9.1.3.2.11. 9.1.3.2.11. Object Group Member Enumeration - 9.1.3.2.33. 9.1.3.2.33. Object Type Enumeration 9.1.3.2.11. 9.1.3.2.12. 9.1.3.2.12. Opaque Data Type Enumeration 9.1.3.2.9. 9.1.3.2.10. 9.1.3.2.10. Operation Enumeration 9.1.3.2.26. 9.1.3.2.27. 9.1.3.2.27. Padding Method Enumeration 9.1.3.2.14. 9.1.3.2.15. 9.1.3.2.15. Put Function Enumeration 9.1.3.2.25. 9.1.3.2.26. 9.1.3.2.26. Query Function Enumeration 9.1.3.2.23. 9.1.3.2.24. 9.1.3.2.24. Recommended Curve Enumeration for ECDSA, ECDH, and ECMQV 9.1.3.2.5. 9.1.3.2.5. 9.1.3.2.5. Result Reason Enumeration 9.1.3.2.28. 9.1.3.2.29. 9.1.3.2.29. Result Status Enumeration 9.1.3.2.27. 9.1.3.2.28. 9.1.3.2.28. Revocation Reason Code Enumeration 9.1.3.2.18. 9.1.3.2.19. 9.1.3.2.19. Secret Data Type Enumeration 9.1.3.2.8. 9.1.3.2.9. 9.1.3.2.9. Split Key Method Enumeration 9.1.3.2.7. 9.1.3.2.8. 9.1.3.2.8. State Enumeration 9.1.3.2.17. 9.1.3.2.18. 9.1.3.2.18. Storage Status Mask 9.1.3.3.2. 9.1.3.3.2. 9.1.3.3.2. Tags 9.1.3.1. 9.1.3.1. 9.1.3.1. TTLV Encoding 9.1. 9.1. 9.1. TTLV Encoding Fields 9.1.1. 9.1.1. 9.1.1. Usage Limits Unit Enumeration 9.1.3.2.30. 9.1.3.2.31. 9.1.3.2.31. Validity Indicator Enumeration 9.1.3.2.22. 9.1.3.2.23. 9.1.3.2.23. Wrapping Method Enumeration 9.1.3.2.4. 9.1.3.2.4. 9.1.3.2.4. XML Encoding 9.2. - - 10 Transport Transport 10 10 10 12 KMIP Server and Client Implementation Conformance Conformance clauses for a KMIP Server 12.1. - - KMIP Client Implementation Conformance - 12.2. 12.2. KMIP Server Implementation Conformance - 12.1. 12.1. Appendix C. Revision History Revision Date Editor Changes Made wd01 21-May-2013 Tim Hudson / Mahadev Karadigudda Converted from draft proposal to OASIS template with minor rewording and inclusion of references to KMIP 1.2 documents wd02 25-June-2013 Tim Hudson Updated test cases and changed how multiple versions of the specification are referenced and added test cases for all versions. wd03 6-August-2013 Tim Hudson Updated to include Permitted Test Case Variations and updated Test Cases based on July 2013 Interop wd04 10-August-2013 Tim Hudson Updated Permitted Test Case Variations wd04a 24-October-2013 Tim Hudson Editorial update to include VendorIdentification in the list of allowed variations as per TC motion. pr01update 11-June-2014 Tim Hudson Updated following Public Review