Key Management Interoperability Protocol Specification Version 1.1

More documents

Recommendations

Info

6666676686696706716726736746756763.15 Certificate IssuerThis attribute is deprecated as of version 1.1 of this specification and MAY be removed from subsequentversions of this specification. The X.509 Certificate Issuer attribute (see Section 3.12) SHOULD be usedinstead.The Certificate Issuer attribute is a structure (see Table 67) used to identify the issuer of a certificate,containing the Issuer Distinguished Name (i.e., from the Issuer field of the certificate). It MAY include oneor more alternative names (e.g., email address, IP address, DNS name) for the issuer of the certificate(i.e., from the Issuer Alternative Name extension within the certificate). The server SHALL set thesevalues based on the information it extracts from a certificate that is created as a result of a Certify or aRe-certify operation or is sent as part of a Register operation. These values SHALL NOT be changed ordeleted before the object is destroyed.Certificate IssuerObject Encoding REQUIREDCertificate IssuerDistinguished NameCertificate IssuerAlternative NameStructureText StringText StringYesNo, MAY be repeated677Table 66: Certificate Issuer Attribute StructureSHALL always have a valueInitially set byModifiable by serverModifiable by clientDeletable by clientMultiple instances permittedWhen implicitly setApplies to Object TypesYesServerNoNoNoNoRegister, Certify, Re-certifyCertificates678679680681682683Table 67: Certificate Issuer Attribute Rules3.16 Digital Signature AlgorithmThe Digital Signature Algorithm identifies the digital signature algorithm associated with a digitally signedobject (e.g., Certificate). This attribute SHALL be set by the server when the object is created orregistered and then SHALL NOT be changed or deleted before the object is destroyed.ObjectEncodingDigital Signature Algorithm Enumeration, see 9.1.3.2.7684Table 68: Digital Signature Algorithm Attributekmip-spec-v1.1-cos01 21 September 2012Standards Track Work Product Copyright © OASIS Open 2012. All Rights Reserved. Page 42 of 164
SHALL always have a valueInitially set byModifiable by serverModifiable by clientDeletable by clientMultiple instances permittedWhen implicitly setApplies to Object TypesYesServerNoNoNoYes for PGP certificates. Nofor X.509 certificates.Certify, Re-certify, RegisterCertificates685686687688689690691692693694695696697698699700701Table 69: Digital Signature Algorithm Attribute Rules3.17 DigestThe Digest attribute is a structure (see Table 70) that contains the digest value of the key or secret data(i.e., digest of the Key Material), certificate (i.e., digest of the Certificate Value), or opaque object (i.e.,digest of the Opaque Data Value). If the Key Material is a Byte String, then the Digest Value SHALL becalculated on this Byte String. If the Key Material is a structure, then the Digest Value SHALL becalculated on the TTLV-encoded (see Section 9.1) Key Material structure. The Key Format Type field inthe Digest attribute indicates the format of the Managed Object from which the Digest Value wascalculated. Multiple digests MAY be calculated using different algorithms listed in Section 9.1.3.2.16and/or key format types listed in Section 9.1.3.2.3. If this attribute exists, then it SHALL have a mandatoryattribute instance computed with the SHA-256 hashing algorithm. For objects registered by a client, theserver SHALL compute the digest of the mandatory attribute instance using the Key Format Type of theregistered object. In all other cases, the server MAY use any Key Format Type when computing thedigest of the mandatory attribute instance, provided it is able to serve the object to clients in that sameformat. The digest(s) are static and SHALL be set by the server when the object is created or registered,provided that the server has access to the Key Material or the Digest Value (possibly obtained via out-ofbandmechanisms).DigestObject Encoding REQUIREDHashing AlgorithmStructureEnumeration, see9.1.3.2.16Digest Value Byte String Yes, if the server has access tothe Digest Value or the KeyMaterial (for keys and secretdata), the Certificate Value (forcertificates) or the OpaqueData Value (for opaqueobjects).Key Format TypeEnumeration, see9.1.3.2.3YesYes, if the Managed Object is akey or secret data object.702Table 70: Digest Attribute Structurekmip-spec-v1.1-cos01 21 September 2012Standards Track Work Product Copyright © OASIS Open 2012. All Rights Reserved. Page 43 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 and 16: 18818919019119219319419519619719819
Page 17 and 18: 23723823924024124224324424524624724
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 41: SHALL always have a valueInitially
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 83 and 84: Response PayloadObject REQUIRED Des
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?