REST API - create
  1. Operations
  2. esx
  3. attestation
  4. tpm2
  5. ca certificates

esx attestation tpm2 ca certificates: create

Add a new TPM CA certificate.

Request:

HTTP request

POST https://{server}/api/esx/attestation/tpm2/ca-certificates
{
    "name" : "obj-103",
    "cert_chain" : {
        "certs" : [
            "string",
            "string"
        ]
    }
}

Body Parameters:

Name Type Description
bold = required
- create_spec The new CA certificate details.
-.name string A unique name for the TPM CA certificate.

When clients pass a value of this structure as a parameter, the field must be an identifier for the resource type: com.vmware.esx.attestation.tpm2.ca_certificates. When operations return a value of this structure as a result, the field will be an identifier for the resource type: com.vmware.esx.attestation.tpm2.ca_certificates.
-.cert_chain x509_cert_chain The CA certificate chain.

Certificates may either be added one at a time, or as a chain. Adding the certificates as a chain allows the group to be managed as a whole. For example, an entire chain can be deleted in one delete operation.

When certificates are added one at a time, the order must be root first, followed by any intermediates. The intermediates certificates must also be ordered in the direction from root to leaf.

Similarly, when added as a chain the list must be ordered in the direction from root to leaf.

Optional. If unset creation will fail.
-.cert_chain.certs string[] A list of certificates each in PEM format.

Certificates must be ordered from the root first.

Response:

HTTP Status Code: 204

Headers:

None

Type:

None

Errors:

HTTP Status Code Type Description
400 already_exists if the certificate name exists.
500 error if there is a generic error.
400 invalid_argument if the configuration is invalid.
401 unauthenticated if the caller is not authenticated.
403 unauthorized if the caller is not authorized.