Key Management Interoperability Protocol Specification Version 1.1

More documents

Recommendations

Info

2182192202212.1.2 CredentialA Credential is a structure (see Table 3) used for client identification purposes and is not managed by thekey management system (e.g., user id/password pairs, Kerberos tokens, etc). It MAY be used forauthentication purposes as indicated in [KMIP-Prof].CredentialObject Encoding REQUIREDCredential TypeCredential ValueStructureEnumeration, see9.1.3.2.1Varies. Structure forUsername andPasswordCredential Type.YesYes222223224225226227228229230231232233234235236Table 3: Credential Object StructureIf the Credential Type in the Credential is Username and Password, then Credential Value is a structureas shown in Table 4. The Username field identifies the client, and the Password field is a secret thatauthenticates the client.Credential ValueObject Encoding REQUIREDStructureUsername Text String YesPassword Text String NoTable 4: Credential Value Structure for the Username and Password CredentialIf the Credential Type in the Credential is Device, then Credential Value is a structure as shown in Table5. One or a combination of the Device Serial Number, Network Identifier, Machine Identifier, and MediaIdentifier SHALL be unique. Server implementations MAY enforce policies on uniqueness for individualfields. Optionally a shared secret or password MAY also be used to authenticate the client.Credential ValueObject Encoding REQUIREDDevice SerialNumberStructureText StringNoPassword Text String NoDevice Identifier Text String NoNetwork Identifier Text String NoMachine Identifier Text String NoMedia Identifier Text String NoTable 5: Credential Value Structure for the Device Credential2.1.3 Key BlockA Key Block object is a structure (see Table 6) used to encapsulate all of the information that is closelyassociated with a cryptographic key. It contains a Key Value of one of the following Key Format Types:Raw – This is a key that contains only cryptographic key material, encoded as a string of bytes.kmip-spec-v1.1-cos01 21 September 2012Standards Track Work Product Copyright © OASIS Open 2012. All Rights Reserved. Page 16 of 164
237238239240241242243244245246247248249250251252253254255256 Opaque – This is an encoded key for which the encoding is unknown to the key managementsystem. It is encoded as a string of bytes. PKCS1 – This is an encoded private key, expressed as a DER-encoded ASN.1 PKCS#1 object. PKCS8 – This is an encoded private key, expressed as a DER-encoded ASN.1 PKCS#8 object,supporting both the RSAPrivateKey syntax and EncryptedPrivateKey. X.509 – This is an encoded object, expressed as a DER-encoded ASN.1 X.509 object. ECPrivateKey – This is an ASN.1 encoded elliptic curve private key. Several Transparent Key types – These are algorithm-specific structures containing definedvalues for the various key types, as defined in Section 2.1.7 Extensions – These are vendor-specific extensions to allow for proprietary or legacy key formats.The Key Block MAY contain the Key Compression Type, which indicates the format of the elliptic curvepublic key. By default, the public key is uncompressed.The Key Block also has the Cryptographic Algorithm and the Cryptographic Length of the key containedin the Key Value field. Some example values are: RSA keys are typically 1024, 2048 or 3072 bits in length 3DES keys are typically from 112 to 192 bits (depending upon key length and the presence ofparity bits) AES keys are 128, 192 or 256 bits in lengthThe Key Block SHALL contain a Key Wrapping Data structure if the key in the Key Value field is wrapped(i.e., encrypted, or MACed/signed, or both).Key BlockObject Encoding REQUIREDKey Format TypeKey CompressionTypeKey ValueCryptographicAlgorithmCryptographicLengthStructureEnumeration, see9.1.3.2.3Enumeration, see9.1.3.2.2Byte String: forwrapped Key Value;Structure: forplaintext Key Value,see 2.1.4Enumeration, see9.1.3.2.13IntegerYesNoYesYes, MAY be omitted only ifthis information is availablefrom the Key Value. Doesnot apply to Secret Data orOpaque Objects. If present,the Cryptographic LengthSHALL also be present.Yes, MAY be omitted only ifthis information is availablefrom the Key Value. Doesnot apply to Secret Data orOpaque Objects. If present,the Cryptographic AlgorithmSHALL also be present.Key Wrapping Data Structure, see 2.1.5 No, SHALL only be presentkmip-spec-v1.1-cos01 21 September 2012Standards Track Work Product Copyright © OASIS Open 2012. All Rights Reserved. Page 17 of 164
Page 1 and 2: Key Management InteroperabilityProt
Page 3 and 4: NoticesCopyright © OASIS Open 2012
Page 5 and 6: 3.18.1 Operations outside of operat
Page 7 and 8: 11.8 Certify ......................
Page 9: sanction to perform a security func
Page 13 and 14: 11411511611711811912012112212312412
Page 15: 18818919019119219319419519619719819
Page 19 and 20: 28628728828929029129229329429529629
Page 21 and 22: Value SHALL be TTLVencoded.32632732
Page 23 and 24: Object Encoding REQUIREDKey Materia
Page 25 and 26: 3763773782.1.7.11 Transparent ECDH
Page 27 and 28: Object Encoding REQUIREDSymmetric K
Page 29 and 30: 47447547647747847948048148248348448
Page 31 and 32: 50150250350450550650750850951051151
Page 33 and 34: SHALL always have a valueInitially
Page 35 and 36: 558559key contained within the Cert
Page 37 and 38: 577578579580581582583584585586X9, I
Page 39 and 40: 609Table 56: X.509 Certificate Iden
Page 45 and 46: 71571671771871972072172272372472572
Page 47 and 48: Default Operation Policy for Privat
Page 51 and 52: 81881982082182282382482582682782882
Page 53 and 54: 892893object is destroyed. This att
Page 57 and 58: 944945946indicates when the key man
Page 59 and 60: 9709719729733.34 FreshThe Fresh att
Page 61 and 62: Application SpecificInformationObje
Page 65 and 66: Request PayloadObject REQUIRED Desc
Page 67 and 68:
Attribute REQUIRED SHALL contain th
Page 69 and 70:
1152115311541155115611571158As a re
Page 71 and 72:
AttributePrivate Key UniqueIdentifi
Page 73 and 74:
management server.11941195119611971
Page 75 and 76:
12361237123812391240124112421243124
Page 77 and 78:
12881289129012911292129312941295129
Page 79 and 80:
13241325132613271328132913301331133
Page 81 and 82:
Request PayloadObject REQUIRED Desc
Page 83 and 84:
Response PayloadObject REQUIRED Des
Page 85 and 86:
Request PayloadObject REQUIRED Desc
Page 87 and 88:
Response PayloadObject REQUIRED Des
Page 89 and 90:
15371538153915401541154215431544154
Page 91 and 92:
1588158915901591159215931594a list
Page 93 and 94:
16231624162516261627162816291630163
Page 95 and 96:
16651666166716681669167016711672167
Page 97 and 98:
17211722172317241725172617271728172
Page 99 and 100:
Option17911792179317941795Table 201
Page 101 and 102:
Request Batch ItemObject REQUIRED i
Page 103 and 104:
18311832183318341835183618371838183
Page 105 and 106:
18811882188318841885188618871888188
Page 107 and 108:
ObjectTagTag ValueCertificate Subje
Page 109 and 110:
ObjectPadding Methodkmip-spec-v1.1-
Page 111 and 112:
TagObjectTag ValueExtension Type420
Page 113 and 114:
19379.1.3.2.4 Wrapping Method Enume
Page 115 and 116:
19469.1.3.2.8 Split Key Method Enum
Page 117 and 118:
RC4 00000016RC5 00000017SKIPJACK 00
Page 119 and 120:
19649.1.3.2.17 Key Role Type Enumer
Page 121 and 122:
19759.1.3.2.21 Derivation Method En
Page 123 and 124:
19879.1.3.2.27 Operation Enumeratio
Page 125 and 126:
19939.1.3.2.30 Batch Error Continua
Page 127 and 128:
200820092010201110 TransportKMIP Se
Page 129 and 130:
Operation Failed20172018Table 249:
Page 131 and 132:
202411.5 Re-keyError Definition Res
Page 133 and 134:
203011.8 CertifyError Definition Re
Page 135 and 136:
Key Wrapping Specification contains
Page 137 and 138:
205011.18 Obtain LeaseError Definit
Page 139 and 140:
a certificate listOne or more of th
Page 141 and 142:
20952096209720982099210021012102210
Page 143 and 144:
CertificateSymmetric KeyPublic KeyP
Page 145 and 146:
22092210Appendix C. Tag Cross-Refer
Page 147 and 148:
Object Defined Type NotesInitializa
Page 149 and 150:
Object Defined Type NotesResult Mes
Page 151 and 152:
221322142215Appendix D. Operations
Page 153 and 154:
22192220222122222223222422252226222
Page 155 and 156:
22932294229522962297229822992300230
Page 157 and 158:
23482349235023512352235323542355235
Page 159 and 160:
24322433243424352436243724382439244
Page 161 and 162:
25162517251825192520252125222523252
Page 163 and 164:
2591Appendix G. Revision HistoryRev
show all

Key Management Interoperability Protocol Specification Version 1.1

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?