2.1.1 Table : Template Object Structure Secret Data A Managed Cryptographic Object containing a shared secret value that is not a key or certificate (e.g., a password). The Key Block of the Secret Data object contains a Key Value of the Secret Data Type. The Key Value MAY be wrapped. Object Encoding REQUIRED Secret Data Structure Secret Data Type Enumeration, see Yes 9.1.3.2.9 Key Block Structure, see 2.1.3 Yes Table : Secret Data Object Structure Opaque Object A Managed Object that the key management server is possibly not able to interpret. The context information for this object MAY be stored and retrieved using Custom Attributes. Object Encoding REQUIRED Opaque Object Structure Opaque Data Type Enumeration, see Yes 9.1.3.2.10 Opaque Data Value Byte String Yes Table : Opaque Object Structure PGP Key A Managed Cryptographic Object that is a text-based representation of a PGP key. The Key Block field, indicated below, will contain the ASCII-armored export of a PGP key in the format as specified in RFC 4880. It MAY contain only a public key block, or both a public and private key block. Two different versions of PGP keys, version 3 and version 4, MAY be stored in this Managed Cryptographic Object. KMIP implementers SHOULD treat the Key Block field as an opaque blob. PGP-aware KMIP clients SHOULD take on the responsibility of decomposing the Key Block into other Managed Cryptographic Objects (Public Keys, Private Keys, etc.). Object Encoding REQUIRED PGP Key Structure PGP Key Version Integer Yes Key Block Structure, see 2.1.3 Yes Table : PGP Key Object Structure
2.1.1 Table : Template Object Structure Secret Data A Managed Cryptographic Object containing a shared secret value that is not a key or certificate (e.g., a password). The Key Block of the Secret Data object contains a Key Value of the Secret Data Type. The Key Value MAY be wrapped. Object Encoding REQUIRED Secret Data Structure Secret Data Type Enumeration, see 9.1.3.2.9 Yes Key Block Structure, see 2.1.3 Yes Table : Secret Data Object Structure Opaque Object A Managed Object that the key management server is possibly not able to interpret. The context information for this object MAY be stored and retrieved using Custom Attributes. Object Encoding REQUIRED Opaque Object Structure Opaque Data Type Enumeration, see 9.1.3.2.10 Yes Opaque Data Value Byte String Yes Table : Opaque Object Structure PGP Key A Managed Cryptographic Object that is a text-based representation of a PGP key. The Key Block field, indicated below, will contain the ASCII-armored export of a PGP key in the format as specified in RFC 4880. It MAY contain only a public key block, or both a public and private key block. Two different versions of PGP keys, version 3 and version 4, MAY be stored in this Managed Cryptographic Object. KMIP implementers SHOULD treat the Key Block field as an opaque blob. PGP-aware KMIP clients SHOULD take on the responsibility of decomposing the Key Block into other Managed Cryptographic Objects (Public Keys, Private Keys, etc.). Object Encoding REQUIRED PGP Key Structure PGP Key Version Integer Yes Key Block Structure, see 2.1.3 Yes Table : PGP Key Object Structure