- URL:
- https://<root>/machines/<machine>/sslcertificates/importExistingServerCertificate
- Methods:
POST- Version Introduced:
- 12.0
Description
The import operation imports an existing server certificate, stored in the PKCS #12 format, into the keystore. If the certificate is a CA signed certificate, you must first import the CA Root or Intermediate certificate using the Import Root Certificate operation.
Request parameters
| Parameter | Details |
|---|---|
| A unique name for the certificate that easily identifies it. Example |
| The password to unlock the file containing the certificate. Example |
| The multi-part POST parameter containing the certificate file. |
| Specifies if the root or intermediate certificates included inside the existing certificate file should also be imported. By default, the parameter is set to Values: |
(Required) | The response format. The default response format is Values: |
(Required) | Users interacting programmatically with this endpoint must generate a token that must be included as a request parameter. A token can be obtained using the Generate Token operation. |
Example usage
The following is a sample POST request for the import operation:
POST /<context>/admin/machines/ORGANIZATION.EXAMPLE.COM/sslcertificates/importExistingServerCertificates HTTP/1.1
Host: organization.example.com
Content-Type: multipart/form-data; boundary=----boundary
------boundary
Content-Disposition: form-data; name="certPassword"
certPassword
------boundary
Content-Disposition: form-data; name="alias"
existingCert
------boundary
Content-Disposition: form-data; name="certFile"; filename=""
Content-Type: application/octet-stream
certFile.pfx
------boundary
Content-Disposition: form-data; name="importCertificateChain"
true
------boundary
Content-Disposition: form-data; name="f"
pjson
------boundaryJSON Response example
{"status": "success"}