REST API - create-task

vcenter trusted infrastructure trust authority clusters attestation tpm2 ca certificates: create-task

Add a new TPM CA certificate on a cluster. This operation was added in vSphere API 7.0.0.

Request:

HTTP request

POST https://{server}/api/vcenter/trusted-infrastructure/trust-authority-clusters/{cluster}/attestation/tpm2/ca-certificates

?vmw-task=true
{
    "name""obj-103",
    "cert_chain"{
        "cert_chain"[
            "string",
            "string"
        ]
    }
}

Path Parameters

Name Type Description
Required
cluster string The id of the cluster on which the operation will be executed.

Body Parameters:

Name Type Description
bold = required
- create_spec The new CA certificate details.
-.name string A unique name for the TPM CA certificate. This attribute was added in vSphere API 7.0.0.

When clients pass a value of this structure as a parameter, the field must be an identifier for the resource type: com.vmware.vcenter.trusted_infrastructure.trust_authority_clusters.attestation.tpm2.CaCertificate. When operations return a value of this structure as a result, the field will be an identifier for the resource type: com.vmware.vcenter.trusted_infrastructure.trust_authority_clusters.attestation.tpm2.CaCertificate.

-.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.

. This attribute was added in vSphere API 7.0.0.

Optional. If unset creation will fail.

-.cert_chain.cert_chain string[] Certificate chain in base64 format. This attribute was added in vSphere API 7.0.0.

Response:

HTTP Status Code: 202

Response Body Structure:

"obj-103"

Headers:

None

Type:

Name Type Description
bold = required
- string

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 or the cluster id is empty.
404 not_found if cluster doesn't match to any cluster in the vCenter.
401 unauthenticated if the caller is not authenticated.